Index Modulesedit

Index Modules are modules created per index and control all aspects related to an index.

Index Settingsedit

Index level settings can be set per-index. Settings may be:

They can only be set at index creation time or on a closed index.
They can be changed on a live index using the update-index-settings API.

Changing static or dynamic index settings on a closed index could result in incorrect settings that are impossible to rectify without deleting and recreating the index.

Static index settingsedit

Below is a list of all static index settings that are not associated with any specific index module:

The number of primary shards that an index should have. Defaults to 5. This setting can only be set at index creation time. It cannot be changed on a closed index. Note: the number of shards are limited to 1024 per index. This limitation is a safety limit to prevent accidental creation of indices that can destabilize a cluster due to resource allocation. The limit can be modified by specifying export ES_JAVA_OPTS="-Des.index.max_number_of_shards=128" system property on every node that is part of the cluster.
[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Whether or not shards should be checked for corruption before opening. When corruption is detected, it will prevent the shard from being opened. Accepts:
(default) Don’t check for corruption when opening a shard.
Check for physical corruption.
Check for both physical and logical corruption. This is much more expensive in terms of CPU and memory usage.

Check for both physical and logical corruption. Segments that were reported as corrupted will be automatically removed. This option may result in data loss. Use with extreme caution!

Checking shards may take a lot of time on large indices.

The default value compresses stored data with LZ4 compression, but this can be set to best_compression which uses DEFLATE for a higher compression ratio, at the expense of slower stored fields performance.
The number of shards a custom routing value can go to. Defaults to 1 and can only be set at index creation time. This value must be less than the index.number_of_shards unless the index.number_of_shards value is also 1. See Routing to an index partition for more details about how this setting is used.

Dynamic index settingsedit

Below is a list of all dynamic index settings that are not associated with any specific index module:

The number of replicas each primary shard has. Defaults to 1.
Auto-expand the number of replicas based on the number of available nodes. Set to a dash delimited lower and upper bound (e.g. 0-5) or use all for the upper bound (e.g. 0-all). Defaults to false (i.e. disabled).
How often to perform a refresh operation, which makes recent changes to the index visible to search. Defaults to 1s. Can be set to -1 to disable refresh.
The maximum value of from + size for searches to this index. Defaults to 10000. Search requests take heap memory and time proportional to from + size and this limits that memory. See Scroll or Search After for a more efficient alternative to raising this.
The maximum value of window_size for rescore requests in searches of this index. Defaults to index.max_result_window which defaults to 10000. Search requests take heap memory and time proportional to max(window_size, from + size) and this limits that memory.
Set to true to make the index and index metadata read only, false to allow writes and metadata changes.
Set to true to disable read operations against the index.
Set to true to disable write operations against the index.
Set to true to disable index metadata reads and writes.
Maximum number of refresh listeners available on each shard of the index. These listeners are used to implement refresh=wait_for.

Settings in other index modulesedit

Other index settings are available in index modules:

Settings to define analyzers, tokenizers, token filters and character filters.
Index shard allocation
Control over where, when, and how shards are allocated to nodes.
Enable or disable dynamic mapping for an index.
Control over how shards are merged by the background merge process.
Configure custom similarity settings to customize how search results are scored.
Control over how slow queries and fetch requests are logged.
Configure the type of filesystem used to access shard data.
Control over the transaction log and background flush operations.