# Node won't start up due to dupliate alias/index names

**URL:** <https://discuss.elastic.co/t/node-wont-start-up-due-to-dupliate-alias-index-names/174548>\
**Category:** Elasticsearch\
**Created:** [March 29, 2019, 2:15pm UTC](https://discuss.elastic.co/t/node-wont-start-up-due-to-dupliate-alias-index-names/174548 "2019-03-29T14:15:48Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [March 29, 2019, 7:22pm UTC](https://discuss.elastic.co/t/node-wont-start-up-due-to-dupliate-alias-index-names/174548/17 "2019-03-29T19:22:10Z")

</div>

Is this cluster in `yellow` or `green` health? If `yellow`, does the [allocation explain API](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-allocation-explain.html) shed any light on why it's not assigning anything to the wiped node? If `green` you might still get some useful information out of the allocation explain API if you try and ask it about a specific shard; if not, try [manually migrating a shard](https://www.elastic.co/guide/en/elasticsearch/reference/current/cluster-reroute.html) and see whether that works.

One possibility is that [delayed allocation](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/delayed-allocation.html) is temporarily preventing any shard movement, if you restarted the node quickly enough. Another possibility is that [allocation or rebalancing are disabled](https://www.elastic.co/guide/en/elasticsearch/reference/6.7/shards-allocation.html).

---

_[View the full topic](https://discuss.elastic.co/t/node-wont-start-up-due-to-dupliate-alias-index-names/174548)._