# V8 - breaking changes - dangling indexes?

**URL:** <https://discuss.elastic.co/t/v8-breaking-changes-dangling-indexes/247551>\
**Category:** Elasticsearch\
**Created:** [September 4, 2020, 1:49pm UTC](https://discuss.elastic.co/t/v8-breaking-changes-dangling-indexes/247551 "2020-09-04T13:49:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\
**Post date:** [September 4, 2020, 1:49pm UTC](https://discuss.elastic.co/t/v8-breaking-changes-dangling-indexes/247551/1 "2020-09-04T13:49:17Z")

</div>

Upgraded to 7.9.1 this morning and had a bit of a shock when my data wasn't reloading. Finally RTFM and saw the note about dangling indexes no longer reloaded by default. Oh boy.

Anyway - when v8 rolls around - how are we to deal with clusters that get into a 'bad state' and have to be reloaded? I run everything on kubernetes and - while rarely - it does happen that I lose the master node and have to restart everything. This typically means reloading all the data and letting elastic sort it out.

What's the plan for such a scenario going forward?

---

<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:** [October 2, 2020, 1:49pm UTC](https://discuss.elastic.co/t/v8-breaking-changes-dangling-indexes/247551/2 "2020-10-02T13:49:24Z")

</div>

Closed on October 2, 2020, 1:49pm UTC

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