# ElasticSearch Docker - To DAEMON or not to DAEMON? **URL:** \ **Category:** Elasticsearch\ **Created:** [February 14, 2019, 7:53pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481 "2019-02-14T19:53:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\ **Post date:** [February 14, 2019, 7:53pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/1 "2019-02-14T19:53:50Z")
Hello - We'er considering moving our current EC2 Based Stack to Docker. High level topography consists of 5 EC2 Instances with all of them acting as Master/Data Nodes. We have two More Coordinating nodes that direct traffic to the 5 master/data nodes. The Two coordinating nodes are fronted by an ELB. We do get approximately 1 million documents per day which this setup handles with ease. A few questions here. Any insights would prove useful in us progressing: 1. Does it make sense to setup the master/data nodes as DAEMON (thus ensuring we get only 1 task per Instance mimicing our current 1 Node per instance in the EC2 setup?). 2. Will this setup support automatic rollover in case of EC2 AMI Updates (as in at least 1 task/node is remaining alive when others are down during AMI upgrade ?) ---
**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\ **Post date:** [February 15, 2019, 1:58pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/2 "2019-02-15T13:58:29Z")
any input would be helpful ---
**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:** [February 15, 2019, 8:33pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/3 "2019-02-15T20:33:35Z")
If you're installing from a DEB/RPM then you might as well use the included service/daemon. If you have multiple nodes down at one time, then your cluster may be in a yellow or red state, that will impact the availability of the services it provides. ---
**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\ **Post date:** [February 15, 2019, 8:56pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/4 "2019-02-15T20:56:03Z")
Thanks @warkolm. The intent here is to support a "Rolling upgrade" and prevent a Red state whenever we upgrade the stack to a newer AMI for example. ---
**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:** [February 15, 2019, 8:57pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/5 "2019-02-15T20:57:18Z")
The follow [https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/setup-upgrade.html) and you should be ok 🙂 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 15, 2019, 8:57pm UTC](https://discuss.elastic.co/t/elasticsearch-docker-to-daemon-or-not-to-daemon/168481/6 "2019-03-15T20:57:19Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.