Unasigned shards


(Juan Díaz González) #1

If for example I add a new node I have unasigned shards although in the elasticsearch configuration (elasticsearch.yml) I have this wrote paremeter:

index.routing.allocation.disable_allocation: false

It does not works I have unnasigned shards.

So I executed a script to recollate all shards:

NODE="Node_name"
IFS=$'\n'
for line in $(curl -s 'localhost:9200/_cat/shards' | fgrep UNASSIGNED); do
  INDEX=$(echo $line | (awk '{print $1}'))
  SHARD=$(echo $line | (awk '{print $2}'))

  curl -XPOST 'localhost:9200/_cluster/reroute' -d '{
     "commands": [
        {
            "allocate": {
                "index": "'$INDEX'",
                "shard": '$SHARD',
                "node": "'$NODE'",
                "allow_primary": true
          }
        }
    ]
  }'
done

So in this way I have all shards recollated. And my question is if this could give me problems in a future because I want to have a structure of parent/child and the parent and the child they need to be in the same shard to the routing by parent or child works correctly or any other type problem.

Thanks in advance


(Mark Walkom) #2

It won't impact P&C as the routing they use is a little different.


(Juan Díaz González) #3

Ok, thanks for your help.

Best regards

Juan


(system) #4