Document how to set ES_TMPDIR in the service file #93121
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Today we suggest that users set `ES_TMPDIR` using `export`, which only works if you're running things directly from the shell. Yet most users encountering `ES_TMPDIR` problems seem to on RHEL and trying to run things via `systemd`, for whom the `export` suggestion doesn't work. This commit adds to the docs a suggestion of how to adjust the `systemd` service file to set the appropriate environment variable. Relates elastic#80651
DaveCTurner
added
>docs
|
Documentation preview: |
elasticsearchmachine
added
Team:Core/Infra
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
DaveCTurner
added
the
auto-backport-and-merge
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 23, 2023
Today we suggest that users set `ES_TMPDIR` using `export`, which only works if you're running things directly from the shell. Yet most users encountering `ES_TMPDIR` problems seem to on RHEL and trying to run things via `systemd`, for whom the `export` suggestion doesn't work. This commit adds to the docs a suggestion of how to adjust the `systemd` service file to set the appropriate environment variable. Relates elastic#80651
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this pull request
Jan 23, 2023
Today we suggest that users set `ES_TMPDIR` using `export`, which only works if you're running things directly from the shell. Yet most users encountering `ES_TMPDIR` problems seem to on RHEL and trying to run things via `systemd`, for whom the `export` suggestion doesn't work. This commit adds to the docs a suggestion of how to adjust the `systemd` service file to set the appropriate environment variable. Relates elastic#80651
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 23, 2023
Today we suggest that users set `ES_TMPDIR` using `export`, which only works if you're running things directly from the shell. Yet most users encountering `ES_TMPDIR` problems seem to on RHEL and trying to run things via `systemd`, for whom the `export` suggestion doesn't work. This commit adds to the docs a suggestion of how to adjust the `systemd` service file to set the appropriate environment variable. Relates #80651
elasticsearchmachine
pushed a commit
that referenced
this pull request
Jan 23, 2023
Today we suggest that users set `ES_TMPDIR` using `export`, which only works if you're running things directly from the shell. Yet most users encountering `ES_TMPDIR` problems seem to on RHEL and trying to run things via `systemd`, for whom the `export` suggestion doesn't work. This commit adds to the docs a suggestion of how to adjust the `systemd` service file to set the appropriate environment variable. Relates #80651
rjernst
added a commit
that referenced
this pull request
Jan 24, 2023
The systemd unit file is part of the Elasticsearch package and should not be edited. Instead, we recommend creating a service override file. This commit tweaks the docs for setting tmp dir with systemd to use the override file instead of editing the unit file. relates #93121
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Jan 24, 2023
…c#93211) The systemd unit file is part of the Elasticsearch package and should not be edited. Instead, we recommend creating a service override file. This commit tweaks the docs for setting tmp dir with systemd to use the override file instead of editing the unit file. relates elastic#93121
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Jan 24, 2023
…c#93211) The systemd unit file is part of the Elasticsearch package and should not be edited. Instead, we recommend creating a service override file. This commit tweaks the docs for setting tmp dir with systemd to use the override file instead of editing the unit file. relates elastic#93121
jpountz
pushed a commit
to jpountz/elasticsearch
that referenced
this pull request
Feb 2, 2023
…c#93211) The systemd unit file is part of the Elasticsearch package and should not be edited. Instead, we recommend creating a service override file. This commit tweaks the docs for setting tmp dir with systemd to use the override file instead of editing the unit file. relates elastic#93121
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Today we suggest that users set
ES_TMPDIRusingexport, which only works if you're running things directly from the shell. Yet most users encounteringES_TMPDIRproblems seem to on RHEL and trying to run things viasystemd, for whom theexportsuggestion doesn't work.This commit adds to the docs a suggestion of how to adjust the
systemdservice file to set the appropriate environment variable.Relates #80651