[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.
This commit is contained in:
Areek Zillur 2016-09-14 15:56:46 -04:00
parent 5d373e7f94
commit 9b17242b5d
1 changed files with 4 additions and 0 deletions

View File

@ -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 must be installed on every node in the cluster. After installation, each
node must be restarted before the plugin becomes visible. 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: This documentation distinguishes two categories of plugins:
Core Plugins:: This category identifies plugins that are part of Elasticsearch Core Plugins:: This category identifies plugins that are part of Elasticsearch