# ElasticSearch S3 Snapshot - Which node to run this on?

**URL:** <https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701>\
**Category:** Elasticsearch\
**Created:** [February 27, 2018, 5:16pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701 "2018-02-27T17:16:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [February 27, 2018, 5:16pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701/1 "2018-02-27T17:16:00Z")

</div>

Hello All,  
I have this ES stack configuration - am implementing the s3-repository plugin. I had a question around this! This is my Stack Config (AWS EC2):

> 2X CO Nodes (running curator for Rollover/Delete Indexes)  
> 5X MASTER+DATA Nodes

The question I had was - that if I do implement the repository-s3 plugin - where would I be running the curator job to take periodic snapshots? Lets say I ran it on the Coordinating Nodes (2 Nodes as indicated above) - since the two CO Nodes are IDENTICALLY created via Cloudformation - they both have the same curator cron running and I dont have a way to tell Cloudformation to run Curator on One CO instance and not another.

**Given this, and the fact curator is running on BOTH CO nodes, what would happen if the same cron curator fires snapshot at the same time** (Which is what I suspect will happen since both nodes have the identical curator cron settings and the s3-respository plugin)?

---

<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:** [February 27, 2018, 5:38pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701/2 "2018-02-27T17:38:45Z")

</div>

One will fail because of the already running job, so they won't conflict 🙂

---

<div class="post-metadata">

**Author:** ![titan1978](https://avatars.discourse-cdn.com/v4/letter/t/c37758/32.png) [@titan1978](https://discuss.elastic.co/u/titan1978)\
**Post date:** [February 27, 2018, 5:39pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701/3 "2018-02-27T17:39:35Z")

</div>

Nice! thank you. A quick follow up : Documentation states taht the plugin needs to be installed in ALL the nodes of the cluster! Does this imply the Coordinating node as well? (should've asked this question first). Does it matter?

---

<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:** [February 27, 2018, 5:40pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701/4 "2018-02-27T17:40:06Z")

</div>

Yep, every single node in the cluster 🙂

---

<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:** [March 27, 2018, 5:40pm UTC](https://discuss.elastic.co/t/elasticsearch-s3-snapshot-which-node-to-run-this-on/121701/5 "2018-03-27T17:40:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
