From 7b0a259b2cd9c8da3da9ed44605b4c24bbbda93c Mon Sep 17 00:00:00 2001 From: Ryan Ernst Date: Thu, 20 Jun 2019 14:27:07 -0700 Subject: [PATCH] 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 --- docs/reference/setup/secure-settings.asciidoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/reference/setup/secure-settings.asciidoc b/docs/reference/setup/secure-settings.asciidoc index 4e3799db75b..82b61848a84 100644 --- a/docs/reference/setup/secure-settings.asciidoc +++ b/docs/reference/setup/secure-settings.asciidoc @@ -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: Only some settings are designed to be read from the keystore. See -documentation for each setting to see if it is supported as part of the keystore. +IMPORTANT: Only some settings are designed to be read from the keystore. However, +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 Elasticsearch.