From 9b17242b5d9c931177181bcec409899f7f48316e Mon Sep 17 00:00:00 2001 From: Areek Zillur Date: Wed, 14 Sep 2016 15:56:46 -0400 Subject: [PATCH] [DOC] Add note for full cluster restart for installing plugins using custom metadata Currently, we check if a node has the same set of custom metadata as the master before joining the cluster. This implies freshly installing a plugin that has its custom metadata requires a full cluster restart. --- docs/plugins/index.asciidoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/plugins/index.asciidoc b/docs/plugins/index.asciidoc index 9dd8045746f..94f36a95c9d 100644 --- a/docs/plugins/index.asciidoc +++ b/docs/plugins/index.asciidoc @@ -16,6 +16,10 @@ Plugins contain JAR files, but may also contain scripts and config files, and must be installed on every node in the cluster. After installation, each node must be restarted before the plugin becomes visible. +NOTE: A full cluster restart is required for installing plugins that have +custom cluster state metadata, such as X-Pack. It is still possible to upgrade +such plugins with a rolling restart. + This documentation distinguishes two categories of plugins: Core Plugins:: This category identifies plugins that are part of Elasticsearch