2015-06-22 17:49:45 -04:00
|
|
|
[[misc-cluster]]
|
|
|
|
=== Miscellaneous cluster settings
|
|
|
|
|
|
|
|
[[cluster-read-only]]
|
|
|
|
==== Metadata
|
|
|
|
|
|
|
|
An entire cluster may be set to read-only with the following _dynamic_ setting:
|
|
|
|
|
|
|
|
`cluster.blocks.read_only`::
|
|
|
|
|
|
|
|
Make the whole cluster read only (indices do not accept write
|
|
|
|
operations), metadata is not allowed to be modified (create or delete
|
|
|
|
indices).
|
|
|
|
|
2017-05-16 11:34:37 -04:00
|
|
|
`cluster.blocks.read_only_allow_delete`::
|
|
|
|
|
|
|
|
Identical to `cluster.blocks.read_only` but allows to delete indices
|
|
|
|
to free up resources.
|
|
|
|
|
2015-06-22 17:49:45 -04:00
|
|
|
WARNING: Don't rely on this setting to prevent changes to your cluster. Any
|
|
|
|
user with access to the <<cluster-update-settings,cluster-update-settings>>
|
|
|
|
API can make the cluster read-write again.
|
|
|
|
|
|
|
|
|
2016-05-04 15:21:47 -04:00
|
|
|
[[cluster-max-tombstones]]
|
|
|
|
==== Index Tombstones
|
|
|
|
|
2016-09-21 09:27:18 -04:00
|
|
|
The cluster state maintains index tombstones to explicitly denote indices that
|
|
|
|
have been deleted. The number of tombstones maintained in the cluster state is
|
2016-05-04 15:21:47 -04:00
|
|
|
controlled by the following property, which cannot be updated dynamically:
|
|
|
|
|
|
|
|
`cluster.indices.tombstones.size`::
|
|
|
|
|
2016-09-21 09:27:18 -04:00
|
|
|
Index tombstones prevent nodes that are not part of the cluster when a delete
|
|
|
|
occurs from joining the cluster and reimporting the index as though the delete
|
|
|
|
was never issued. To keep the cluster state from growing huge we only keep the
|
|
|
|
last `cluster.indices.tombstones.size` deletes, which defaults to 500. You can
|
|
|
|
increase it if you expect nodes to be absent from the cluster and miss more
|
|
|
|
than 500 deletes. We think that is rare, thus the default. Tombstones don't take
|
2016-05-04 15:21:47 -04:00
|
|
|
up much space, but we also think that a number like 50,000 is probably too big.
|
|
|
|
|
2015-06-22 17:49:45 -04:00
|
|
|
[[cluster-logger]]
|
|
|
|
==== Logger
|
|
|
|
|
|
|
|
The settings which control logging can be updated dynamically with the
|
|
|
|
`logger.` prefix. For instance, to increase the logging level of the
|
|
|
|
`indices.recovery` module to `DEBUG`, issue this request:
|
|
|
|
|
2015-07-14 12:14:09 -04:00
|
|
|
[source,js]
|
2015-06-22 17:49:45 -04:00
|
|
|
-------------------------------
|
|
|
|
PUT /_cluster/settings
|
|
|
|
{
|
|
|
|
"transient": {
|
2016-09-14 08:08:49 -04:00
|
|
|
"logger.org.elasticsearch.indices.recovery": "DEBUG"
|
2015-06-22 17:49:45 -04:00
|
|
|
}
|
|
|
|
}
|
|
|
|
-------------------------------
|
2016-09-21 09:27:18 -04:00
|
|
|
// CONSOLE
|