# Elasticsearch and restarting

**URL:** <https://discuss.elastic.co/t/elasticsearch-and-restarting/17630>\
**Category:** Elasticsearch\
**Created:** [May 20, 2014, 6:55pm UTC](https://discuss.elastic.co/t/elasticsearch-and-restarting/17630 "2014-05-20T18:55:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Dunbar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brian_dunbar/32/1550_2.png) [@Brian\_Dunbar](https://discuss.elastic.co/u/Brian_Dunbar)\
**Post date:** [May 20, 2014, 6:55pm UTC](https://discuss.elastic.co/t/elasticsearch-and-restarting/17630/1 "2014-05-20T18:55:20Z")

</div>

Hi,

- Elasticsearch 1.1
- Two-node cluster.
- Ubuntu 12.04

Last night, I installed the marvel plugin, after which my automation script  
(1) issued 'service elasticsearch restart' within seconds of each other.

After which, in Paramedic, both nodes showed 'no data' (using Paramedic)  
which was cause for a few minutes of 'whoa'.

Restarted node-1, waited for it to init, then restarted node-2 and all was  
well.

Question is: is restarting ES in a cluster mode using the built-in service  
facility the 'right' way? Or would it be better to halt / start using the  
API? [2]

Thanks,

~brian

(1) Ansible

(2) [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html)

--  
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/4129ab92-b88a-4466-a6d6-1b2689a5ce02%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4129ab92-b88a-4466-a6d6-1b2689a5ce02%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [May 20, 2014, 10:49pm UTC](https://discuss.elastic.co/t/elasticsearch-and-restarting/17630/2 "2014-05-20T22:49:38Z")

</div>

Using service is fine, but you can only issue a shutdown with the API, not  
start up.

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 21 May 2014 04:55, Brian Dunbar [brian.dunbar@gmail.com](mailto:brian.dunbar@gmail.com) wrote:

> Hi,
> 
> - Elasticsearch 1.1
> - Two-node cluster.
> - Ubuntu 12.04
> 
> Last night, I installed the marvel plugin, after which my automation  
> script (1) issued 'service elasticsearch restart' within seconds of each  
> other.
> 
> After which, in Paramedic, both nodes showed 'no data' (using Paramedic)  
> which was cause for a few minutes of 'whoa'.
> 
> Restarted node-1, waited for it to init, then restarted node-2 and all was  
> well.
> 
> Question is: is restarting ES in a cluster mode using the built-in service  
> facility the 'right' way? Or would it be better to halt / start using the  
> API? [2]
> 
> Thanks,
> 
> ~brian
> 
> (1) Ansible
> 
> (2)  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-nodes-shutdown.html)
> 
> --  
> 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/4129ab92-b88a-4466-a6d6-1b2689a5ce02%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/4129ab92-b88a-4466-a6d6-1b2689a5ce02%40googlegroups.com)[https://groups.google.com/d/msgid/elasticsearch/4129ab92-b88a-4466-a6d6-1b2689a5ce02%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/4129ab92-b88a-4466-a6d6-1b2689a5ce02%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/CAEM624b4tpaTE0xGaKdrrghwZp2EzwHy-zasA8CVjMLu2V%2BRtA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624b4tpaTE0xGaKdrrghwZp2EzwHy-zasA8CVjMLu2V%2BRtA%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:28am UTC](https://discuss.elastic.co/t/elasticsearch-and-restarting/17630/3 "2017-07-06T01:28:02Z")

</div>


