Question about unassigned shards


(mark-2) #1

I've spun up a new ES cluster (0.90.5) that consists of two nodes with zone
awareness. I created a test index with 5 shards and 1 replica via the API
which returns successfully. When I examine the cluster health endpoint, the
result shows that the shards are unassigned and remains that way:

{"cluster_name": "mysearchcluster","status": "red","timed_out": false,"
number_of_nodes": 2,"number_of_data_nodes": 2,"active_primary_shards": 0,"
active_shards": 0,"relocating_shards": 0,"initializing_shards": 0,"
unassigned_shards": 10}

There doesn't appear to be anything in the logs that indicate an errors.
Also I cannot (as I would expect) able to access the index via curl.

I'm sure I'm missing something obvious here but just looking for help as to
what step I may have missed in setting up this two node cluster.

Thanks in advance!

--
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.


(Jörg Prante) #2

The cluster state is red, so I'm sure there is something in the logs... can
you please give us insight about your logs and the command how you did set
up zone awareness.

Jörg

--
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.


(mark-2) #3

Certainly.

Here's all the log output after a data node restart:
https://gist.github.com/mgreene/6909159

elasticsearch.yml: https://gist.github.com/mgreene/6909279

On Wednesday, October 9, 2013 5:35:26 PM UTC-4, Jörg Prante wrote:

The cluster state is red, so I'm sure there is something in the logs...
can you please give us insight about your logs and the command how you did
set up zone awareness.

Jörg

--
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.


(mark-2) #4

Ok fixed my own problem.

We were missing node.zone in our yml file and had the
'cluster.routing.allocation.awareness.attributes' property set wrong.

On Wednesday, October 9, 2013 6:04:55 PM UTC-4, ma...@evertrue.com wrote:

Certainly.

Here's all the log output after a data node restart:
https://gist.github.com/mgreene/6909159

elasticsearch.yml: https://gist.github.com/mgreene/6909279

On Wednesday, October 9, 2013 5:35:26 PM UTC-4, Jörg Prante wrote:

The cluster state is red, so I'm sure there is something in the logs...
can you please give us insight about your logs and the command how you did
set up zone awareness.

Jörg

--
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.


(system) #5