# Node crashes due to max number of docs exceeded, but ILM should've not let it happen **URL:** \ **Category:** Elasticsearch\ **Created:** [September 28, 2019, 5:54pm UTC](https://discuss.elastic.co/t/node-crashes-due-to-max-number-of-docs-exceeded-but-ilm-shouldve-not-let-it-happen/201499 "2019-09-28T17:54:54Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![anishm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anishm/32/28796_2.png) [@anishm](https://discuss.elastic.co/u/anishm)\ **Post date:** [September 29, 2019, 4:50pm UTC](https://discuss.elastic.co/t/node-crashes-due-to-max-number-of-docs-exceeded-but-ilm-shouldve-not-let-it-happen/201499/3 "2019-09-29T16:50:38Z")
We have been running 7.3 for a month now, and looking at ILM explain results, it is seen that the indices were getting rolled over at 50GB everytime. Even the last index, metricbeat-7.3.0-0000050 rolled over correctly from 49. The 51st rollover also worked as expected. I can't do a dry run on that index now as I had to delete it to get the nodes started. But given that previous rollovers were successful, it might not be a problem with rollover itself? After deleting the old 51 Index, I created a new 51 index to give a write index to the metricbeat-7.3.0 alias and continued indexing data. Now, I do see that 52nd rollover was successfully done today morning. I did see the same problem with an APM (apm-7.3.0-span-0000029) index previously, and hence edited the default lifecycle policy packaged with beats to do a rollover on number of docs as well (default policy rolls over on 50gb) , because I believed that would've been the problem at that time. However, I'll get the ES cluster upgraded to the 7.3.2 patch so that nodes don't crash again. --- _[View the full topic](https://discuss.elastic.co/t/node-crashes-due-to-max-number-of-docs-exceeded-but-ilm-shouldve-not-let-it-happen/201499)._