Too many nodes started up on some data nodes - best approach to fix?

(Josh Harrison) #1

I restarted my cluster the other day, but something odd stuck, resulting in
15/16 data nodes starting up an extra ES instance in the same cluster. This
ended badly as there were two nodes with identical display names, the
system locked up, etc.
When restarting again, to my horror, we were missing shards. I quickly
figured out that the missing shards had gotten moved into the second
instance storage location.
What is the best way to resolve this? Should we either spawn second ES
instances on the culprit machines (with different instance names), or can a
mv escluster/nodes/1/indices/data1/* escluster/nodes/0/indices/data1/
do the job?


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
To view this discussion on the web visit
For more options, visit

(system) #2