# Nodes crash when index reaches 50gb so I would like to auto create indexes is this possible? **URL:** \ **Category:** Elasticsearch\ **Created:** [July 25, 2022, 12:05pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530 "2022-07-25T12:05:56Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![ToonKnight](https://avatars.discourse-cdn.com/v4/letter/t/3e96dc/32.png) [@ToonKnight](https://discuss.elastic.co/u/ToonKnight)\ **Post date:** [July 25, 2022, 12:05pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/1 "2022-07-25T12:05:56Z")
Hey all, I noticed that my nodes crash when my index grows over 50GB, so I would like to create a new index when it reaches 50GB then assign the events-active alias to the new index, and remove that alias from the old index. Would this be possible with Elasticsearch itself, and if so, how? Thanks ---
**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:** [July 25, 2022, 12:13pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/2 "2022-07-25T12:13:27Z")
Which version of Elasticsearch are you using? What does the Elasticsearch logs say? What is the specification of the cluster? ---
**Author:** ![ToonKnight](https://avatars.discourse-cdn.com/v4/letter/t/3e96dc/32.png) [@ToonKnight](https://discuss.elastic.co/u/ToonKnight)\ **Post date:** [July 25, 2022, 12:24pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/3 "2022-07-25T12:24:15Z")
version 7.17.4, the sysops team didn't get any logs, what do you mean by "specification of the cluster" we have 3 masters and 5 data nodes, I was told to automate the process that's all xd, this happens maybe once a month ---
**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:** [July 25, 2022, 12:44pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/4 "2022-07-25T12:44:34Z")
> [@ToonKnight](#): > > the sysops team didn't get any logs How is the cluster deployed? How come no logs are available? Elasticsearch logs generally contain vital information in situations like this. > [@ToonKnight](#): > > what do you mean by "specification of the cluster" How much CPU, RAM and heap do the different node types have? What type of storage is being used? > [@ToonKnight](#): > > I noticed that my nodes crash How many nodes crashed? How did this happen? Do you have any monitoring in place? It sounds odd that a single index going above a specific size would crash the node. Are you using any mapping types that may drive memory usage? ---
**Author:** ![ToonKnight](https://avatars.discourse-cdn.com/v4/letter/t/3e96dc/32.png) [@ToonKnight](https://discuss.elastic.co/u/ToonKnight)\ **Post date:** [July 25, 2022, 1:06pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/5 "2022-07-25T13:06:27Z")
So the data nodes have 30GB ram each, and the master nodes have 8GB ram each. I think they have 4 vcores each, I am not sure about the cores as I don't have access to our AWS environment yet. and apparently, the nodes don't crash, my bad, the index just dies cuz I'm assuming it's hitting our storage limit. So I want to make a new index automatically and move the old index into cold storage maybe. ---
**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:** [July 25, 2022, 1:10pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/6 "2022-07-25T13:10:49Z")
> [@ToonKnight](#): > > So the data nodes have 30GB ram each, and the master nodes have 8GB ram each. I think they have 4 vcores each, What is the heap size? > [@ToonKnight](#): > > and apparently, the nodes don't crash, my bad, the index just dies cuz I'm assuming it's hitting our storage limit. Indices do not die. They may however go read-only if you fill up your storage. How much data does the cluster hold? How much storage does each data node have? Does the index hold immutable data? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 22, 2022, 1:11pm UTC](https://discuss.elastic.co/t/nodes-crash-when-index-reaches-50gb-so-i-would-like-to-auto-create-indexes-is-this-possible/310530/7 "2022-08-22T13:11:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.