# Elasticsearch Cluster Ingest Node Sizing

**URL:** <https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971>\
**Category:** Elasticsearch\
**Tags:** ingest-pipeline\
**Created:** [March 7, 2022, 1:41pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971 "2022-03-07T13:41:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [March 7, 2022, 1:41pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971/1 "2022-03-07T13:41:44Z")

</div>

Hi Team,

We're planning to add a new Ingest node to running ES cluster, this node is dedicated only for data ingestion. How to do capacity planning for ingest node, does this memory optimized or CPU optimized, to ingest Index size of around 1TB into the ES cluster (new Index weekly basis)? Please give me an advice.

Thank you in advance.

---

<div class="post-metadata">

**Author:** ![sagarpatel](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sagarpatel](https://discuss.elastic.co/u/sagarpatel)\
**Post date:** [March 8, 2022, 5:16am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971/2 "2022-03-08T05:16:36Z")

</div>

@chateesh I will say it **depends**. there are multipul fector you need to consider like

- how many ingest\_pipeline you have configured ?

- data complexity

- what enrich processor you are using ? if script then might be it will take more mory.

- any many more ...

Please check this [link](https://www.elastic.co/guide/en/cloud/current/ec-getting-started-profiles.html) for CPU optimized or memory optimized.

---

<div class="post-metadata">

**Author:** ![chateesh](https://avatars.discourse-cdn.com/v4/letter/c/8baadc/32.png) [@chateesh](https://discuss.elastic.co/u/chateesh)\
**Post date:** [March 8, 2022, 3:55pm UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971/3 "2022-03-08T15:55:18Z")

</div>

Thankyou @sagarpatel

It has only one ingest pipeline.

---

<div class="post-metadata">

**Author:** ![sagarpatel](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@sagarpatel](https://discuss.elastic.co/u/sagarpatel)\
**Post date:** [March 9, 2022, 6:55am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971/4 "2022-03-09T06:55:23Z")

</div>

@chateesh You have one pipeline but not sure how many processor it has ? Also, it will depnds on your index ration like per min how many documents are you indexing.

So my suggestion will be do POC with 1 week data and test load on node and based on that decide on node configuration.

Please check [Elastic blog](https://www.elastic.co/blog/benchmarking-and-sizing-your-elasticsearch-cluster-for-logs-and-metrics) which will give you more understanding of benchmarking and sizing 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:** [April 6, 2022, 6:56am UTC](https://discuss.elastic.co/t/elasticsearch-cluster-ingest-node-sizing/298971/5 "2022-04-06T06:56:21Z")

</div>

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