# Cluster state issues on full restart

**URL:** <https://discuss.elastic.co/t/cluster-state-issues-on-full-restart/13217>\
**Category:** Elasticsearch\
**Created:** [August 14, 2013, 7:11pm UTC](https://discuss.elastic.co/t/cluster-state-issues-on-full-restart/13217 "2013-08-14T19:11:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![robert\_3](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/robert_3/32/2132_2.png) [@robert\_3](https://discuss.elastic.co/u/robert_3)\
**Post date:** [August 14, 2013, 7:11pm UTC](https://discuss.elastic.co/t/cluster-state-issues-on-full-restart/13217/1 "2013-08-14T19:11:44Z")

</div>

Hi all,

It seems to me that I may have issues with the cluster state being saved  
between full cluster restarts. This morning after a full cluster restart, I  
noticed the following

[2013-08-14 18:47:16,615][DEBUG][action.admin.indices.create] [node]  
[quizlet] failed to create  
org.elasticsearch.indices.InvalidIndexNameException: [quizlet] Invalid  
index name [quizlet], an alias with the same name already exists  
at  
org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.validate(MetaDataCreateIndexService.java:532)  
at  
org.elasticsearch.cluster.metadata.MetaDataCreateIndexService.access$200(MetaDataCreateIndexService.java:86)  
at  
org.elasticsearch.cluster.metadata.MetaDataCreateIndexService$2.execute(MetaDataCreateIndexService.java:171)  
at  
org.elasticsearch.cluster.service.InternalClusterService$UpdateTask.run(InternalClusterService.java:285)  
at  
org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor.java:143)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown  
Source)  
at java.lang.Thread.run(Unknown Source)

There were 6 of these, one for each non-master node in the cluster, in the  
master's log files. The initial stages of recovery seemed to hang with low  
network traffic for a few minutes, and then started with large amounts of  
traffic and I soon saw the number of active shards increasing in the  
cluster's health status.

Is this expected behavior? I would think that cluster state saving would  
prevent all of the nodes from requesting an index be created which they  
know is an alias.

## Thanks,

Robert Deaton

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [July 6, 2017, 2:21am UTC](https://discuss.elastic.co/t/cluster-state-issues-on-full-restart/13217/2 "2017-07-06T02:21:09Z")

</div>

Closed on July 6, 2017, 2:21am UTC