# New index not forminga nd ending up with High disk watermark

**URL:** <https://discuss.elastic.co/t/new-index-not-forminga-nd-ending-up-with-high-disk-watermark/208386>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [November 18, 2019, 8:07pm UTC](https://discuss.elastic.co/t/new-index-not-forminga-nd-ending-up-with-high-disk-watermark/208386 "2019-11-18T20:07:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehak\_Bhargava](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mehak_bhargava/32/54750_2.png) [@Mehak\_Bhargava](https://discuss.elastic.co/u/Mehak_Bhargava)\
**Post date:** [November 18, 2019, 8:07pm UTC](https://discuss.elastic.co/t/new-index-not-forminga-nd-ending-up-with-high-disk-watermark/208386/1 "2019-11-18T20:07:42Z")

</div>

When I run ES, Kibana, Filebeats my logs are getting collected and passed in real time as I want, but they are all getting collected under an old index-

```auto
yellow open filebeat-7.4.0-2019.11.08-000001 lMcCHhWuT9ecTfsI4OyGEA 1 1 9076656

```

Please help me fix why I cant generate new index per day as this old index has too many doc counts and resulting in High Disk watermark.

---

<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 16, 2019, 8:07pm UTC](https://discuss.elastic.co/t/new-index-not-forminga-nd-ending-up-with-high-disk-watermark/208386/2 "2019-12-16T20:07:44Z")

</div>

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