In a multi node elastic cluster which node (master, hot and warm data nodes, client nodes) the following mail configuration needs to be entered for X-Pack alerting.
Whether the above mentioned email account configuration needs to be entered (elasticsearch.yml) on all nodes or only in the master nodes is fine where the watcher runs.
For the sake of consistency you should put it on all nodes. You have to put it on all nodes that can potentially become master node. Also, from 6.0 onwards the location where watches will be executed will change, so that it makes sense to put this config everywhere just to be future proof.
If you dont want to store this in configuration files, you can also use the cluster update settings API to store the configuration settings. No need for a restart.
Great. Thank you. Where the persistent type of cluster updates are stored? Whether it will survive the node restart.
Also when is the tentative date of BELK 6.0 release.
Felix is right. The persistent updates are written to disk together with the cluster state. This is also the reason why those updates survive full cluster restarts, where as the transient updates do not.
There are no concrete release dates for the Elastic Stack 6.0. Even though we are nearing GA, it will take a few more months until the GA version will be out (and one or more release candidates in between). Nothing more concrete though.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.