Adding new nodes to cluster with unicast without restarting


(Hari Prasad) #1

Hi
I am having an elasticsearch cluster. I am using the unicast to discover
nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my
cluster. I can go for it if i can, in anyway, limit what all nodes join the
cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

--
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/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #2

Yes. Just launch the new node and set its unicast values to other running nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamhari1234@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring transient setting [discovery.zen.ping.unicast.hosts], not dynamically updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my cluster. I can go for it if i can, in anyway, limit what all nodes join the cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.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/01537FBE-A376-4FBA-BD16-5BF0D5476EAC%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Hari Prasad) #3

Is this the case the even if discovery.zen.ping.multicast.enabled is false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:

Yes. Just launch the new node and set its unicast values to other running
nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to
have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad <iamha...@gmail.com <javascript:>> a
écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover
nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my
cluster. I can go for it if i can, in anyway, limit what all nodes join the
cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

--
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.com?utm_medium=email&utm_source=footer
.
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/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #4

yes

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamhari1234@gmail.com) a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:
Yes. Just launch the new node and set its unicast values to other running nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring transient setting [discovery.zen.ping.unicast.hosts], not dynamically updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my cluster. I can go for it if i can, in anyway, limit what all nodes join the cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.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/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.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/etPan.5321bb40.140e0f76.158d%40MacBook-Air-de-David.local.
For more options, visit https://groups.google.com/d/optout.


(Hari Prasad) #5

Ok Thank you :slight_smile:

On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:

yes

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamha...@gmail.com <javascript:>)
a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:

Yes. Just launch the new node and set its unicast values to other
running nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to
have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover
nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my
cluster. I can go for it if i can, in anyway, limit what all nodes join the
cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.com?utm_medium=email&utm_source=footer
.
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.com?utm_medium=email&utm_source=footer
.
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/e0b97af5-eb5c-48c2-b9ca-783f50aab8fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Hari Prasad) #6

Hi
Can you please explain the following
I first started one node with only its ip in unicast host list and
multicast discovery false. The cluster started with one node.
Then I started another node with its unicast host value of node one. This
also joined the cluster.

This is in sync with what you said. But if this is the case the what the
use for setting the multicast as false and setting the unicast host list.
Cant any node join the cluster just like that by setting the unicast to any
node in the cluster. how to limit this.

On Thursday, 13 March 2014 19:46:08 UTC+5:30, Hari Prasad wrote:

Ok Thank you :slight_smile:

On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:

yes

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamha...@gmail.com) a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is
false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:

Yes. Just launch the new node and set its unicast values to other
running nodes.
It will connect to the cluster and the cluster will add him as a new
node.

You don't have to modify existing settings, although you should do it to
have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover
nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my
cluster. I can go for it if i can, in anyway, limit what all nodes join the
cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.com?utm_medium=email&utm_source=footer
.
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.com?utm_medium=email&utm_source=footer
.
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/7af0beb0-880c-4df4-b182-eb026210959b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #7

If the cluster name is different, the new node won't join the cluster.
Also, if you have a security concern, you should restrict network access to your nodes on a transport layer (9300).

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 mars 2014 à 07:11, Hari Prasad iamhari1234@gmail.com a écrit :

Hi
Can you please explain the following
I first started one node with only its ip in unicast host list and multicast discovery false. The cluster started with one node.
Then I started another node with its unicast host value of node one. This also joined the cluster.

This is in sync with what you said. But if this is the case the what the use for setting the multicast as false and setting the unicast host list.
Cant any node join the cluster just like that by setting the unicast to any node in the cluster. how to limit this.

On Thursday, 13 March 2014 19:46:08 UTC+5:30, Hari Prasad wrote:
Ok Thank you :slight_smile:

On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:
yes

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamha...@gmail.com) a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:
Yes. Just launch the new node and set its unicast values to other running nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring transient setting [discovery.zen.ping.unicast.hosts], not dynamically updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my cluster. I can go for it if i can, in anyway, limit what all nodes join the cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.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/7af0beb0-880c-4df4-b182-eb026210959b%40googlegroups.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/67888A41-9415-4F99-B1AE-CEDD0FFC7544%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(Hari Prasad) #8

Is the cluster name the only was to restrict nodes from joining into
cluster, unicast or multicast.

I do have security concern and my concern is is there a way the address it
from elasticsearch itself rather than going into the network layer.
On Friday, 14 March 2014 12:22:52 UTC+5:30, David Pilato wrote:

If the cluster name is different, the new node won't join the cluster.
Also, if you have a security concern, you should restrict network access
to your nodes on a transport layer (9300).

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 mars 2014 à 07:11, Hari Prasad <iamha...@gmail.com <javascript:>> a
écrit :

Hi
Can you please explain the following
I first started one node with only its ip in unicast host list and
multicast discovery false. The cluster started with one node.
Then I started another node with its unicast host value of node one. This
also joined the cluster.

This is in sync with what you said. But if this is the case the what the
use for setting the multicast as false and setting the unicast host list.
Cant any node join the cluster just like that by setting the unicast to
any node in the cluster. how to limit this.

On Thursday, 13 March 2014 19:46:08 UTC+5:30, Hari Prasad wrote:

Ok Thank you :slight_smile:

On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:

yes

--
David Pilato | Technical Advocate | Elasticsearch.com
http://Elasticsearch.com

@dadoonet https://twitter.com/dadoonet | @elasticsearchfrhttps://twitter.com/elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamha...@gmail.com) a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is
false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:

Yes. Just launch the new node and set its unicast values to other
running nodes.
It will connect to the cluster and the cluster will add him as a new
node.

You don't have to modify existing settings, although you should do it
to have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to
discover nodes. Can I add nodes to list dynamically without restarting the
cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring
transient setting [discovery.zen.ping.unicast.hosts], not dynamically
updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join
my cluster. I can go for it if i can, in anyway, limit what all nodes join
the cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.com?utm_medium=email&utm_source=footer
.
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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.com?utm_medium=email&utm_source=footer
.
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 elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7af0beb0-880c-4df4-b182-eb026210959b%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/7af0beb0-880c-4df4-b182-eb026210959b%40googlegroups.com?utm_medium=email&utm_source=footer
.
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/228a8efa-2ba3-4cf2-a244-15ea641dcf2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(David Pilato) #9

AFAIK no but I might be wrong.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 mars 2014 à 07:58, Hari Prasad iamhari1234@gmail.com a écrit :

Is the cluster name the only was to restrict nodes from joining into cluster, unicast or multicast.

I do have security concern and my concern is is there a way the address it from elasticsearch itself rather than going into the network layer.

On Friday, 14 March 2014 12:22:52 UTC+5:30, David Pilato wrote:
If the cluster name is different, the new node won't join the cluster.
Also, if you have a security concern, you should restrict network access to your nodes on a transport layer (9300).

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 14 mars 2014 à 07:11, Hari Prasad iamha...@gmail.com a écrit :

Hi
Can you please explain the following
I first started one node with only its ip in unicast host list and multicast discovery false. The cluster started with one node.
Then I started another node with its unicast host value of node one. This also joined the cluster.

This is in sync with what you said. But if this is the case the what the use for setting the multicast as false and setting the unicast host list.
Cant any node join the cluster just like that by setting the unicast to any node in the cluster. how to limit this.

On Thursday, 13 March 2014 19:46:08 UTC+5:30, Hari Prasad wrote:
Ok Thank you :slight_smile:

On Thursday, 13 March 2014 19:35:52 UTC+5:30, David Pilato wrote:
yes

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet | @elasticsearchfr

Le 13 mars 2014 à 15:00:10, Hari Prasad (iamha...@gmail.com) a écrit:

Is this the case the even if discovery.zen.ping.multicast.enabled is false?

On Thursday, 13 March 2014 19:17:19 UTC+5:30, David Pilato wrote:
Yes. Just launch the new node and set its unicast values to other running nodes.
It will connect to the cluster and the cluster will add him as a new node.

You don't have to modify existing settings, although you should do it to have updated settings in case of restart.

--
David :wink:
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 13 mars 2014 à 14:38, Hari Prasad iamha...@gmail.com a écrit :

Hi
I am having an elasticsearch cluster. I am using the unicast to discover nodes. Can I add nodes to list dynamically without restarting the cluster?
I tried to do this with the prepareUpdateSettings but i got "ignoring transient setting [discovery.zen.ping.unicast.hosts], not dynamically updateable".
Is there any other way to do this without restarting the cluster.

I am not going for multicast because i don't want rouge nodes to join my cluster. I can go for it if i can, in anyway, limit what all nodes join the cluster, other than the cluster name.
Are there any ways to do this.

Thanks
Hari

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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/127e4ba6-3fab-4fca-8595-e4506ef8f101%40googlegroups.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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a5a2de96-f308-495a-8de4-07feca421759%40googlegroups.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 elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7af0beb0-880c-4df4-b182-eb026210959b%40googlegroups.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/228a8efa-2ba3-4cf2-a244-15ea641dcf2e%40googlegroups.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/A53F2D68-C5E7-4714-9DD2-7B24A5E29075%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.


(system) #10