Change node settings at runtime

Is it possible to change node level settings at runtime? Specifically I'm looking to change node.data, node.master, and node.river.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

No, this isn't possible. Changing those settings requires a restart of that
node.

On 11 September 2013 05:03, shadow000fire jason.scheller@gmail.com wrote:

Is it possible to change node level settings at runtime? Specifically I'm
looking to change node.data, node.master, and node.river.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
Met vriendelijke groet,

Martijn van Groningen

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

How hard would it be to change this? Correct me if I'm wrong, but logically it shouldn't be a problem to change those settings at runtime as long as reallocation of shards or rivers (respectively) isn't currently happening. Is that fair?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

How hard would it be to change this? Correct me if I'm wrong, but logically it shouldn't be a problem to change those settings at runtime as long as reallocation of shards or rivers (respectively) isn't currently happening. Is that fair?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

Its actually quite tricky, since it might require a re-election of master
(relocation of data is simpler). Why would you need it thought? Those
settings would sound quite "static", as in if one goes with X masters and N
data nodes, one would probably keep on adding more data nodes.

On Wed, Sep 11, 2013 at 12:56 PM, shadow000fire jason.scheller@gmail.comwrote:

How hard would it be to change this? Correct me if I'm wrong, but
logically it shouldn't be a problem to change those settings at runtime as
long as reallocation of shards or rivers (respectively) isn't currently
happening. Is that fair?

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.