Monday, 13 April 2015

Elasticseach - Shards allocation error

After follow the Guidelines from Elastic documentation. In order to recover unassigned shard on TEST Env elasticsearch cluster. I got this error..

" {"error":"RemoteTransportException[[node01][inet[/ipaddess:9300]][cluster:admin/reroute]]; nested: ElasticsearchIllegalArgumentException[[allocate] trying to allocate a primary shard [.shardname1][0], which is disabled]; ","status":400} "
Resolved with ...

"
#!/bin/bash
for shard in $(curl -XGET http://localhost:9200/_cat/shards | grep UNASSIGNED | awk '{print $2}'); do
  # This have to be commented
  curl -XPOST 'localhost:9200/_cluster/reroute' -d '{
    "commands": [
      {
      "allocate": {
          "index": "index_name",
          "shard": 1,
              "node": "node1",
              "allow_primary": true
          }
        }
    ]
  }'
  sleep 5
done
"

So, I would like to ask you whether, I should try to recover the data or just disable it at all.
:-) Dont worry I managed to fix it and re-assigned the shards ...

Why PM2 Is Not Launching Your Node.js App—and How to Fix It

Why PM2 Is Not Launching Your Node.js App—and How to Fix It Broken Your Node.js PM2 — and How to Fix It Have you ever...