# Optimizing setup which contains a single cold-node

**URL:** <https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006>\
**Category:** Elasticsearch\
**Created:** [June 22, 2020, 6:05am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006 "2020-06-22T06:05:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![victor.nilsson](https://avatars.discourse-cdn.com/v4/letter/v/eb8c5e/32.png) [@victor.nilsson](https://discuss.elastic.co/u/victor.nilsson)\
**Post date:** [June 22, 2020, 6:05am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006/1 "2020-06-22T06:05:12Z")

</div>

Hey there,

We currently have the following setup:

Two hot-nodes ingesting live data. After x amount of days ILM will rollover the indices and then move the indices to a cold-node where we close the indices after 7 days. This works great but i wonder if my setup is working correctly.

For instance, closed indices are still being counted as "active" by looking at the monitoring page and at how many indices our cold-node is having (notice _2392_ shards active for the archive-node):

 ![elk-stack](https://us1.discourse-cdn.com/elastic/original/3X/2/9/299a748d0ef7391cb4e892c1a2f516142992cedb.png)

Is this correct? Should we be freezing the indices instead?  
Also, the archive-node (cold-node) have 16k segments.

---

<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 24, 2020, 4:51am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006/2 "2020-06-24T04:51:06Z")

</div>

Which version of Elasticsearch are you using?

---

<div class="post-metadata">

**Author:** ![victor.nilsson](https://avatars.discourse-cdn.com/v4/letter/v/eb8c5e/32.png) [@victor.nilsson](https://discuss.elastic.co/u/victor.nilsson)\
**Post date:** [June 24, 2020, 11:26am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006/3 "2020-06-24T11:26:15Z")

</div>

We're using Elasticsearch 7.6.0

---

<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 24, 2020, 11:31am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006/4 "2020-06-24T11:31:42Z")

</div>

Recent versions of Elasticsearch keep track of closed and frozen indices to make sure they get replicated on node failures. With only one cold node you do not benefit from that but it is still there and as they therefore need to be tracked they count against the limit. Elasticsearch 7.7 introduced improvements that reduce heap usage significantly so if you upgrade you may be able to simply keep the indices open instead of freezing or closing them.

---

<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 22, 2020, 11:31am UTC](https://discuss.elastic.co/t/optimizing-setup-which-contains-a-single-cold-node/238006/5 "2020-07-22T11:31:45Z")

</div>

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