Elasticsearch head UNASSIGNED


(Mohit Anchlia) #1

I am little confused with elasticsearch head UIs output. I added a new node
and created a new index "test3" with shard: 5 and replica: 1. I also added
a routing rule to only make new node the data node for this test. However,
I am confused with 2 things:

  1. head is showing that my index is spread on the old node as well. I
    expect it to be only on the new node
  2. Some of the shards are showing UNASSIGNED
  3. How to differentiate between a replica and a shard in the UI?

curl -XPUT 10.80.140.86:9200/test3/_settings -d '{

"index.routing.allocation.include.group1" : "group2"

}'

I am also attaching the screen shot of the UI.

--
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 Walkom) #2

Elasticsearch won't store replicas with the primary as it defeats the
purpose of having a replica. So you will either need to remove your replica
or your routing for the unassigned shards to clear up.

(Re #3) I think you mean primary and replica, as a shard can be either.
Primaries have the bold black border in head. You might also want to look
at the kopf plugin which is a rebuilt version of head.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 22 November 2013 08:51, Mohit Anchlia mohitanchlia@gmail.com wrote:

I am little confused with elasticsearch head UIs output. I added a new
node and created a new index "test3" with shard: 5 and replica: 1. I also
added a routing rule to only make new node the data node for this test.
However, I am confused with 2 things:

  1. head is showing that my index is spread on the old node as well. I
    expect it to be only on the new node
  2. Some of the shards are showing UNASSIGNED
  3. How to differentiate between a replica and a shard in the UI?

curl -XPUT 10.80.140.86:9200/test3/_settings -d '{

"index.routing.allocation.include.group1" : "group2"

}'

I am also attaching the screen shot of the UI.

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

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


(Mohit Anchlia) #3

thanks!

On Thu, Nov 21, 2013 at 2:26 PM, Mark Walkom markw@campaignmonitor.comwrote:

Elasticsearch won't store replicas with the primary as it defeats the
purpose of having a replica. So you will either need to remove your replica
or your routing for the unassigned shards to clear up.

(Re #3) I think you mean primary and replica, as a shard can be either.
Primaries have the bold black border in head. You might also want to look
at the kopf plugin which is a rebuilt version of head.

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 22 November 2013 08:51, Mohit Anchlia mohitanchlia@gmail.com wrote:

I am little confused with elasticsearch head UIs output. I added a new
node and created a new index "test3" with shard: 5 and replica: 1. I also
added a routing rule to only make new node the data node for this test.
However, I am confused with 2 things:

  1. head is showing that my index is spread on the old node as well. I
    expect it to be only on the new node
  2. Some of the shards are showing UNASSIGNED
  3. How to differentiate between a replica and a shard in the UI?

curl -XPUT 10.80.140.86:9200/test3/_settings -d '{

"index.routing.allocation.include.group1" : "group2"

}'

I am also attaching the screen shot of the UI.

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

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

--
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) #4