WARNING: Version 0.90 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Directory Layoutedit
The directory layout of an installation is as follows:
| Type | Description | Default Location | Setting |
|---|---|---|---|
home |
Home of elasticsearch installation |
|
|
bin |
Binary scripts including |
|
|
conf |
Configuration files including |
|
|
data |
The location of the data files of each index / shard allocated on the node. Can hold multiple locations. |
|
|
work |
Temporal files that are used by different nodes. |
|
|
logs |
Log files location |
|
|
plugins |
Plugin files location. Each plugin will be contained in a subdirectory. |
|
|
The multiple data locations allows to stripe it. The striping is simple,
placing whole files in one of the locations, and deciding where to place
the file based on the value of the index.store.distributor setting:
-
least_used(default) always selects the directory with the most available space
-
randomselects directories at random. The probability of selecting a particular directory is proportional to amount of available space in this directory.
Note, there are no multiple copies of the same data, in that, its similar to RAID 0. Though simple, it should provide a good solution for people that don’t want to mess with RAID. Here is how it is configured:
path.data: /mnt/first,/mnt/second
Or the in an array format:
path.data: ["/mnt/first", "/mnt/second"]