How to safely apply new configuration from elasticsearch.yml


(David Reagan) #1

I manage my ES cluster using Ansible. Specifically I wrote this
role https://github.com/LaneCommunityCollege/aspects_elasticsearch to do
most of the work for me.

The issue right now is that if I make a change to my elasticsearch.yml
configuration, Ansible automatically issues a 'service elasticsearch
restart' command for me. Normally this isn't a issue, but when the
configuration applies to all the nodes in my cluster, that would restart
the entire cluster. Not really something I'd like to do very often.

Is there a command I can run that would tell ES to load the
elasticsearch.yml configuration without shutting the node down?

Is there a command/script I could run that would check the clusters'
status, if it is not green it would wait and check again, then when it is
green, it would restart the node? (Writing a script to do this is my
current plan, but I'd like to know what more experience users are doing
first.)

I'm running ES 1.1.x on Ubuntu 12.04.

I expect that any configuration management system that deploys
configuration to the elasticsearch.yml file and then restarts the node
would have this same issue. So if you are configuring ES via Puppet, Chef,
or another system, what do you do?

--
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/81bb62ce-3fde-47af-a61e-01d6400dd83b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

The only way to load the config is with a restart of the service.
You could use the cat API to check on the status before reloading -
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/cat-health.html

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 25 July 2014 05:45, David Reagan jerrac@gmail.com wrote:

I manage my ES cluster using Ansible. Specifically I wrote this role
https://github.com/LaneCommunityCollege/aspects_elasticsearch to do most
of the work for me.

The issue right now is that if I make a change to my elasticsearch.yml
configuration, Ansible automatically issues a 'service elasticsearch
restart' command for me. Normally this isn't a issue, but when the
configuration applies to all the nodes in my cluster, that would restart
the entire cluster. Not really something I'd like to do very often.

Is there a command I can run that would tell ES to load the
elasticsearch.yml configuration without shutting the node down?

Is there a command/script I could run that would check the clusters'
status, if it is not green it would wait and check again, then when it is
green, it would restart the node? (Writing a script to do this is my
current plan, but I'd like to know what more experience users are doing
first.)

I'm running ES 1.1.x on Ubuntu 12.04.

I expect that any configuration management system that deploys
configuration to the elasticsearch.yml file and then restarts the node
would have this same issue. So if you are configuring ES via Puppet, Chef,
or another system, what do you do?

--
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/81bb62ce-3fde-47af-a61e-01d6400dd83b%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/81bb62ce-3fde-47af-a61e-01d6400dd83b%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/CAEM624Y18Wn098iO-rdQ-W16wf%3DNqmVdqqm7LmDK3ktVbMhzcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #3