The link you provided is for transient settings, meaning they will reset
once the cluster restarts. Doing this via the configurations file ensures
the settings are loaded back.
As Mark said, this is cluster level settings. If you have nodes with
different HD characteristics you probably want to use percentages for the
watermark values.
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer & Consultant
Author of RavenDB in Action http://manning.com/synhershko/
On Fri, May 16, 2014 at 3:26 PM, Michel Conrad <
michel.conrad@trendiction.com> wrote:
What if I set the option in the configuration file, will it then only
be applied to the node reading the configuration file?
On Fri, May 16, 2014 at 10:36 AM, Mark Walkom markw@campaignmonitor.com
wrote:
It's a cluster level setting, so all nodes use the same one.
As far as I know, there is no node level setting.
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com
On 16 May 2014 17:43, Michel Conrad michel.conrad@trendiction.com
wrote:
Is it possible to specify different thresholds for different nodes in
the cluster? I could not find it in the documentation, when updating
the setting through the cluster settings as described on
Elasticsearch Platform — Find real-time answers at scale | Elastic
the threshold is applied to every node.
When specifing the thresholds through the configuration file, will it
then be only applied to the node reading the configuration? In this
case how to I prevent the cluster settings being applied and
overwriting the configuration file (remove a setting).
Thanks for any thoughts,
Michel
--
You received this message because you are subscribed to the Google
Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAH0sEYgM4%3DmH2cA3wJoBQAmx82ddrz6N%3D8u3XE0EFoKoOwTUUQ%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEM624a6tk9jqGkh_ED%3Dx_bpJPxpiydP9_KxTugrBVZuX5yaCw%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAH0sEYjc5DAO4mW%2B%3DnrgDfxbEd%2BYxwcn1vZ9jXxBNm1N%2BH9%3D1Q%40mail.gmail.com
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAHTr4ZtTZfb%2B0uJSxohd685pCAcEgxZXSg_SYeu9izq%3D4_1zjQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.