Clarify unsupported secure settings behavior (#43454)
This commit tweaks the docs for secure settings to ensure the user is aware adding non secure settings to the keystore will result in elasticsearch not starting. fixes #43328 Co-Authored-By: James Rodewig <james.rodewig@elastic.co>
This commit is contained in:
parent
21515b9ff1
commit
7b0a259b2c
|
@ -7,8 +7,12 @@ keystore and the `elasticsearch-keystore` tool to manage the settings in the key
|
||||||
|
|
||||||
NOTE: All commands here should be run as the user which will run Elasticsearch.
|
NOTE: All commands here should be run as the user which will run Elasticsearch.
|
||||||
|
|
||||||
NOTE: Only some settings are designed to be read from the keystore. See
|
IMPORTANT: Only some settings are designed to be read from the keystore. However,
|
||||||
documentation for each setting to see if it is supported as part of the keystore.
|
the keystore has no validation to block unsupported settings.
|
||||||
|
Adding unsupported settings to the keystore will cause {es}
|
||||||
|
Additional unsupported settings being added to the keystore will cause Elasticsearch
|
||||||
|
to fail to start. See documentation for each setting to see if it is supported
|
||||||
|
as part of the keystore.
|
||||||
|
|
||||||
NOTE: All the modifications to the keystore take affect only after restarting
|
NOTE: All the modifications to the keystore take affect only after restarting
|
||||||
Elasticsearch.
|
Elasticsearch.
|
||||||
|
|
Loading…
Reference in New Issue