# Coordinating Node Role in Data Ingestion

**URL:** <https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157>\
**Category:** Elasticsearch\
**Created:** [June 27, 2021, 5:53pm UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157 "2021-06-27T17:53:03Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikasp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikasp/32/90872_2.png) [@vikasp](https://discuss.elastic.co/u/vikasp)\
**Post date:** [June 27, 2021, 5:53pm UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/1 "2021-06-27T17:53:03Z")

</div>

Can anybody please help me understand the role of coordinating node with respect to data ingestion.  
I understand the role of the coordinating nodes in terms of search queries (the scatter and gather phases),  
But what is the node's role in ingestion

---

<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:** [June 28, 2021, 1:51am UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/2 "2021-06-28T01:51:43Z")

</div>

If it's a coordinating only then it'd likely pass the request to a node that has the ingest role enabled.

---

<div class="post-metadata">

**Author:** ![vikasp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikasp/32/90872_2.png) [@vikasp](https://discuss.elastic.co/u/vikasp)\
**Post date:** [June 28, 2021, 3:54am UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/3 "2021-06-28T03:54:09Z")

</div>

Lets say Its a coordinating node only, and no ingest nodes available, data is directly coming from logstash,  
say we are getting an ingestion request from logstash to a large index with say 10 shards, how does it play out. It would be helpful to understand with an example like how the documentation explains it with respect to search.

Thanks in advance.

---

<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:** [June 28, 2021, 5:36am UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/4 "2021-06-28T05:36:30Z")

</div>

I don't know sorry. I would imagine it'd respond with an error, you'd need to test it.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [June 28, 2021, 6:08am UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/5 "2021-06-28T06:08:05Z")

</div>

Assuming you are not using ingest pipelines it will act as a coordinator just as for searches. The bulk request will be split up so that the requests are sent to the appropriate primary shard. The results are then gathered and a response returned.

---

<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 26, 2021, 6:08am UTC](https://discuss.elastic.co/t/coordinating-node-role-in-data-ingestion/277157/6 "2021-07-26T06:08:29Z")

</div>

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