# Regarding Coordinator Node Heap Usage

**URL:** <https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080>\
**Category:** Elasticsearch\
**Created:** [October 11, 2018, 3:02pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080 "2018-10-11T15:02:08Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [October 30, 2018, 9:48pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/21 "2018-10-30T21:48:25Z")

</div>

Ok thx @warkolm. But we're also going to move to using ingestion pipelines. If we do that will the ingest nodes maintain a bulk queue and apply backpressure through rejections?

---

<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:** [October 30, 2018, 9:56pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/22 "2018-10-30T21:56:26Z")

</div>

They will yes, I just don't know if that's a specific ingest-only bulk pool or if it uses the main one. The docs don't mention a custom one so I'd say it's the latter.

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [October 31, 2018, 8:04am UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/23 "2018-10-31T08:04:12Z")

</div>

So, if we set up an ingestion pipeline that does nothing that will allow our ingest nodes to apply backpressure?

---

<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:** [October 31, 2018, 8:18am UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/24 "2018-10-31T08:18:51Z")

</div>

You mean it does nothing _but_ ingest?

---

<div class="post-metadata">

**Author:** ![dawiro](https://avatars.discourse-cdn.com/v4/letter/d/71e660/32.png) [@dawiro](https://discuss.elastic.co/u/dawiro)\
**Post date:** [October 31, 2018, 3:44pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/25 "2018-10-31T15:44:51Z")

</div>

Yes, ingestion but with no grok'ing or filtering (yet)

---

<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:** [October 31, 2018, 8:11pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/26 "2018-10-31T20:11:02Z")

</div>

Then yes.

---

<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:** [November 28, 2018, 8:11pm UTC](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080/27 "2018-11-28T20:11:06Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/regarding-coordinator-node-heap-usage/152080.md?page=1)