Cluster state issues on full restart

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.
For more options, visit https://groups.google.com/groups/opt_out.