Is it safe to change node names in an existing ElasticSearch cluster

Hi !

Is it safe to change the node names of my 3 nodes in an existing
elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy"
Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and
then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then
change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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 mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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/1916C068-085D-4F86-B877-FE4F9003B46D%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

1 Like

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml
file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and
after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a
maintenance windows, change all names, and then restart the ES cluster
nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:

Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during
this, you should disable allocation.

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

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund <je.we...@gmail.com
<javascript:>> a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing
elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy"
Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and
then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then
change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a maintenance windows, change all names, and then restart the ES cluster nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:
Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund <je.we...@gmail.com <javascript:>> a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name http://node.name/: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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 mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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/639A13FF-A6F9-4309-9D8A-B4C83184D6EE%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the
nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes
first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:

Have a look at
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund <je.we...@gmail.com
<javascript:>> a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the
elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and
after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a
maintenance windows, change all names, and then restart the ES cluster
nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:

Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during
this, you should disable allocation.

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

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a écrit
:

Hi !

Is it safe to change the node names of my 3 nodes in an existing
elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy"
Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and
then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then
change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

You can change safely elasticsearch.yml file while elasticsearch is running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:
Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a maintenance windows, change all names, and then restart the ES cluster nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:
Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%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/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

I understand that, but is it safe to change all the nodenames and restart all the nodes at the same time ?

Skickat från min iPhone 6.

19 feb 2015 kl. 07:47 skrev David Pilato david@pilato.fr:

You can change safely elasticsearch.yml file while elasticsearch is running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:
Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a maintenance windows, change all names, and then restart the ES cluster nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:
Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr.
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/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

You should define this in that case: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html#recover-after

But it's not anymore a rolling upgrade, right? Your service will be down for some seconds/minutes I guess.

David

Le 19 févr. 2015 à 07:52, Jan-Erik Westlund je.westlund@gmail.com a écrit :

I understand that, but is it safe to change all the nodenames and restart all the nodes at the same time ?

Skickat från min iPhone 6.

19 feb 2015 kl. 07:47 skrev David Pilato david@pilato.fr:

You can change safely elasticsearch.yml file while elasticsearch is running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:
Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a maintenance windows, change all names, and then restart the ES cluster nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:
Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr.
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/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.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/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Correct, in that case, it will not be a rolling upgrade :wink: The service
will be down for a few minutes.
Can I then change all the nodenames, and the start the services on all the
nodes with the new names without messing things up ?

2015-02-19 7:58 GMT+01:00 David Pilato david@pilato.fr:

You should define this in that case:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html#recover-after

But it's not anymore a rolling upgrade, right? Your service will be down
for some seconds/minutes I guess.

David

Le 19 févr. 2015 à 07:52, Jan-Erik Westlund je.westlund@gmail.com a
écrit :

I understand that, but is it safe to change all the nodenames and restart
all the nodes at the same time ?

Skickat från min iPhone 6.

19 feb 2015 kl. 07:47 skrev David Pilato david@pilato.fr:

You can change safely elasticsearch.yml file while elasticsearch is
running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a
écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the
nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes
first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:

Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/cluster-nodes-shutdown.html#rolling
restart_of_nodes_full_cluster_restart

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

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a écrit
:

Thanks David !

All my "Recovery Throttling settings" are default in the
elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and
after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a
maintenance windows, change all names, and then restart the ES cluster
nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:

Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during
this, you should disable allocation.

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

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a
écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing
elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy"
Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and
then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then
change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9eca2130-030d-468c-825d-b66c8766ba4a%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr?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/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.com
https://groups.google.com/d/msgid/elasticsearch/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr?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/CAH7LSTZJuoD0kCvMnQpJ2jJAt_egjwaRf2fNrg%3Dkfh8y9DF4xg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Yes.

David

Le 19 févr. 2015 à 08:56, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Correct, in that case, it will not be a rolling upgrade :wink: The service will be down for a few minutes.
Can I then change all the nodenames, and the start the services on all the nodes with the new names without messing things up ?

2015-02-19 7:58 GMT+01:00 David Pilato david@pilato.fr:

You should define this in that case: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html#recover-after

But it's not anymore a rolling upgrade, right? Your service will be down for some seconds/minutes I guess.

David

Le 19 févr. 2015 à 07:52, Jan-Erik Westlund je.westlund@gmail.com a écrit :

I understand that, but is it safe to change all the nodenames and restart all the nodes at the same time ?

Skickat från min iPhone 6.

19 feb 2015 kl. 07:47 skrev David Pilato david@pilato.fr:

You can change safely elasticsearch.yml file while elasticsearch is running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:
Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html#_rolling_restart_of_nodes_full_cluster_restart

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during a maintenance windows, change all names, and then restart the ES cluster nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:
Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving during this, you should disable allocation.

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy" Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr.
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/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr.
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/CAH7LSTZJuoD0kCvMnQpJ2jJAt_egjwaRf2fNrg%3Dkfh8y9DF4xg%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/33739DCE-DDCE-48D7-B24F-38C628EFEB75%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

Ok, thanks again.

2015-02-19 9:06 GMT+01:00 David Pilato david@pilato.fr:

Yes.

David

Le 19 févr. 2015 à 08:56, Jan-Erik Westlund je.westlund@gmail.com a
écrit :

Correct, in that case, it will not be a rolling upgrade :wink: The service
will be down for a few minutes.
Can I then change all the nodenames, and the start the services on all the
nodes with the new names without messing things up ?

2015-02-19 7:58 GMT+01:00 David Pilato david@pilato.fr:

You should define this in that case:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html#recover-after

But it's not anymore a rolling upgrade, right? Your service will be down
for some seconds/minutes I guess.

David

Le 19 févr. 2015 à 07:52, Jan-Erik Westlund je.westlund@gmail.com a
écrit :

I understand that, but is it safe to change all the nodenames and restart
all the nodes at the same time ?

Skickat från min iPhone 6.

19 feb 2015 kl. 07:47 skrev David Pilato david@pilato.fr:

You can change safely elasticsearch.yml file while elasticsearch is
running.
This file is only loaded when elasticsearch starts.

David

Le 19 févr. 2015 à 07:33, Jan-Erik Westlund je.westlund@gmail.com a
écrit :

Hi again !

Thanks for Rolling restart info, that was really helpful.
But since the "elasticsearch.yml" file is managed by Puppet, all the
nodenames will change pretty much at the same time !
So in my case it would be best to shutdown the ES daemon on all nodes
first, apply the Puppet changes and then start the ES cluster again...
Is it safe to do so ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:44:35 UTC+1 skrev David Pilato:

Have a look at http://www.elasticsearch.org/guide/en/elasticsearch/
reference/current/cluster-nodes-shutdown.html#rolling
restart_of_nodes_full_cluster_restart

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

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

Le 18 févr. 2015 à 16:37, Jan-Erik Westlund je.we...@gmail.com a
écrit :

Thanks David !

All my "Recovery Throttling settings" are default in the
elasticsearch.yml file.
How do I disable allocation, in a running production environment ?
Do I need to disable allocation first, restart each node / daemon, and
after rename the nodes ?

Or maybe it would be better to down the ES cluster (all 3 nodes) during
a maintenance windows, change all names, and then restart the ES cluster
nodes again ?

//Jan-Erik

Den onsdag 18 februari 2015 kl. 16:18:42 UTC+1 skrev David Pilato:

Yes. It’s safe.
You can do it one at a time.

If you already have data around and don’t want your shards moving
during this, you should disable allocation.

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

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

Le 18 févr. 2015 à 16:14, Jan-Erik Westlund je.we...@gmail.com a
écrit :

Hi !

Is it safe to change the node names of my 3 nodes in an existing
elasticsearch 1.4.0 cluster ?

The reason is to get rid of the random names like: Elizabeth "Betsy"
Braddock, Franz Kafka, etc...

Is it just to set the node.name: "server name" in elasticsearch.yml
and then restart the daemon ?
Do I do it one node at the time, or do I need down the cluster and then
change all node names, and then bring up the cluster again ?

//Jan-Erik

--
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/0bed6a3d-9315-4060-9585-cf68907f844b%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/0bed6a3d-9315-4060-9585-cf68907f844b%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/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%
40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/a79c0ae3-d786-4bf4-80cb-61acdb8804d3%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/9eca2130-030d-468c-825d-b66c8766ba4a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9eca2130-030d-468c-825d-b66c8766ba4a%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/48CE0F31-5B2A-4F47-B210-3786C818C834%40pilato.fr?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/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.com
https://groups.google.com/d/msgid/elasticsearch/F8956AA2-2066-407B-A42C-A5D68097B1E9%40gmail.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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/FC54F28D-05E7-4EEE-A7C3-7364DF4D863A%40pilato.fr?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/CAH7LSTZJuoD0kCvMnQpJ2jJAt_egjwaRf2fNrg%3Dkfh8y9DF4xg%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAH7LSTZJuoD0kCvMnQpJ2jJAt_egjwaRf2fNrg%3Dkfh8y9DF4xg%40mail.gmail.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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/ZjOHjpXVZ00/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/33739DCE-DDCE-48D7-B24F-38C628EFEB75%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/33739DCE-DDCE-48D7-B24F-38C628EFEB75%40pilato.fr?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/CAH7LSTaNRr_UWOjhucySubR8%2BzB3tsy6q00js1DbAezcpzhdOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.