Diagnosing why one node is getting no shards

I have an Elasticsearch cluster of five nodes. I have the configuration on
each set the same with 5 shards per index and 4 replicas. The idea is that
every node will have every shard.

Four of my nodes have five shards. One node has ALL of them primary. One
node has NOTHING. And then, of course, I have 5 unallocated shards.

I reload a new index every day and this is exactly how it allocates shards
every time.

I need to find out why the one node isn't getting any shards. That's bad.

It would be easy for me to ask why this is happening - and if anyone knows,
that would be fantastic. But as I can't seem to find ANYTHING online or in
the documentation to explain this, I must ask, perhaps, how I can diagnose
it? Any clues? Anything I can look at to give a clue here?

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/76d46f15-447c-4797-860e-fc8ae3ec09dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

I found my own answer - but for anyone who might have this issue, ensure
that all nodes are running the same version of ES. Apparently when they're
not, older versions will not get shards.

Who knew? :slight_smile:

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/9789c9d0-4b41-481b-826a-b11ee45b649a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

1 Like

That is touched on in this doc page
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html

"The upgrades sometimes include upgrades to the Lucene libraries used by
Elasticsearch to access the index files, and after an index file has been
updated to work with a new version of Lucene, it may not be accessible to
the versions of Lucene present in earlier Elasticsearch releases."

On 18 November 2014 07:13, Christopher Ambler const.dogberry@gmail.com
wrote:

I found my own answer - but for anyone who might have this issue, ensure
that all nodes are running the same version of ES. Apparently when they're
not, older versions will not get shards.

Who knew? :slight_smile:

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/9789c9d0-4b41-481b-826a-b11ee45b649a%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/9789c9d0-4b41-481b-826a-b11ee45b649a%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAF3ZnZ%3DDPzvhfOdLmORVvjBujFXwOmpcCCLyotoJHy_Bov%3DctA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.