honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-09 22:45:04 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenSearch/docs/reference/setup/important-settings/es-tmpdir.asciidoc

26 lines
1.2 KiB
Plaintext
Raw Normal View History

Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
[[es-tmpdir]]
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
[discrete]
=== Temporary directory settings
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
By default, {es} uses a private temporary directory that the startup
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
script creates immediately below the system temporary directory.
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
On some Linux distributions, a system utility will clean files and directories
from `/tmp` if they have not been recently accessed. This behavior can lead to
the private temporary directory being removed while {es} is running if
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
features that require the temporary directory are not used for a long time.
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
Removing the private temporary directory causes problems if a feature that
requires this directory is subsequently used.
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
If you install {es} using the `.deb` or `.rpm` packages and run it
under `systemd`, the private temporary directory that {es} uses
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
is excluded from periodic cleanup.
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
If you intend to run the `.tar.gz` distribution on Linux or MacOS for
an extended period, consider creating a dedicated temporary
directory for {es} that is not under a path that will have old files
Add temporary directory cleanup workarounds (#32615) On some Linux distributions tmpfiles.d cleans files and directories under /tmp if they haven't been accessed for 10 days. This can cause problems for ML as ML is currently the only component that uses the temp directory more than a few seconds after startup. If you didn't open an ML job for 10 days and then tried to open one then the temp directory would have been deleted. This commit prevents the problem occurring in the case of Elasticsearch being managed by systemd, as systemd private temp directories are not subject to periodic cleanup (by default). Additionally there are now some docs to warn people about the risk and suggest a manual mitigation for .tar.gz users.
2018-08-07 16:59:56 +01:00
and directories cleaned from it. This directory should have permissions set
[DOCS] [7.10] Combining important config settings into a single page (#63849) (#63883) * [DOCS] Combining important config settings into a single page (#63849) * Combining important config settings into a single page. * Updating ids for two pages causing link errors and implementing redirects. * Updating links to use IDs instead of xrefs.
2020-10-19 12:59:44 -04:00
so that only the user that {es} runs as can access it. Then, set the
`$ES_TMPDIR` environment variable to point to this directory before starting
{es}.
Reference in New Issue Copy Permalink