# How big should an index be for 2x data node cluster

**URL:** <https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531>\
**Category:** Elasticsearch\
**Created:** [October 26, 2022, 2:03pm UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531 "2022-10-26T14:03:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![landychev](https://avatars.discourse-cdn.com/v4/letter/l/a88e57/32.png) [@landychev](https://discuss.elastic.co/u/landychev)\
**Post date:** [October 26, 2022, 2:03pm UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/1 "2022-10-26T14:03:10Z")

</div>

I did a query at my elastic nodes today.

```auto
curl -X GET "http://$IP:9200/_cat/indices?v"

```

I did see that i have some index that are 80-90Gb and some are smaller.  
Is that normal or do i have some wrong settings ?  
Does the big index impact on search from graylog/kibana ?  
I have a Rotation period for 1day and Max number of indices set to 60 so i could have log for 60days and Max. number of segments set to 1 and shards to 4

---

<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, 2022, 2:22am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/2 "2022-10-31T02:22:36Z")

</div>

Are you using ILM here?

---

<div class="post-metadata">

**Author:** ![landychev](https://avatars.discourse-cdn.com/v4/letter/l/a88e57/32.png) [@landychev](https://discuss.elastic.co/u/landychev)\
**Post date:** [November 7, 2022, 8:29am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/3 "2022-11-07T08:29:18Z")

</div>

What is ILM ?  
/Alex

---

<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:** [November 7, 2022, 8:35am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/4 "2022-11-07T08:35:35Z")

</div>

[ILM](https://www.elastic.co/guide/en/elasticsearch/reference/current/index-lifecycle-management.html) \<

---

<div class="post-metadata">

**Author:** ![landychev](https://avatars.discourse-cdn.com/v4/letter/l/a88e57/32.png) [@landychev](https://discuss.elastic.co/u/landychev)\
**Post date:** [November 7, 2022, 8:56am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/5 "2022-11-07T08:56:02Z")

</div>

We are not Using ILM, we are using graylog that manage our retation.

---

<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:** [November 7, 2022, 9:00am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/6 "2022-11-07T09:00:14Z")

</div>

You will need to ask the graylog team then, that rotation setup is not anything we can assist with sorry.

But an index of 90GB isn't terrible, even if we do recommend 30-50GB ourselves.

---

<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:** [December 5, 2022, 9:00am UTC](https://discuss.elastic.co/t/how-big-should-an-index-be-for-2x-data-node-cluster/317531/7 "2022-12-05T09:00:54Z")

</div>

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