mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-05 20:48:22 +00:00
008296e2b6
This commit reorganizes some of the content in the configuring Elasticsearch section of the docs. The changes are: - move JVM options out of system configuration into configuring Elasticsearch - move JVM options to its own page of the docs - move configuring the heap to important Elasticsearch settings - move configuring the heap to its own page of the docs - move all important settings to individual pages in the docs - remove bootstrap.memory_lock from important settings, this is covered in the swap section of system configuration Relates #27755
32 lines
1.1 KiB
Plaintext
32 lines
1.1 KiB
Plaintext
[[path-settings]]
|
|
=== `path.data` and `path.logs`
|
|
|
|
If you are using the `.zip` or `.tar.gz` archives, the `data` and `logs`
|
|
directories are sub-folders of `$ES_HOME`. If these important folders are left
|
|
in their default locations, there is a high risk of them being deleted while
|
|
upgrading Elasticsearch to a new version.
|
|
|
|
In production use, you will almost certainly want to change the locations of the
|
|
data and log folder:
|
|
|
|
[source,yaml]
|
|
--------------------------------------------------
|
|
path:
|
|
logs: /var/log/elasticsearch
|
|
data: /var/data/elasticsearch
|
|
--------------------------------------------------
|
|
|
|
The RPM and Debian distributions already use custom paths for `data` and `logs`.
|
|
|
|
The `path.data` settings can be set to multiple paths, in which case all paths
|
|
will be used to store data (although the files belonging to a single shard will
|
|
all be stored on the same data path):
|
|
|
|
[source,yaml]
|
|
--------------------------------------------------
|
|
path:
|
|
data:
|
|
- /mnt/elasticsearch_1
|
|
- /mnt/elasticsearch_2
|
|
- /mnt/elasticsearch_3
|
|
-------------------------------------------------- |