Find the unassigned shards:
curl -XGET http://<ip_address>:9200/_cat/shards | grep UNASSIGNED
The resolution to this was the below command, change the index and shard
number to any primary unassigned shards
curl -XPOST '<ip_address>:9200/_cluster/reroute' -d '{"commands":
[{"allocate": {"index": "graylog_400", "shard": 0, "node": "Dragon Lord",
"allow_primary": true }}]}'
On Monday, February 15, 2016 at 9:19:39 PM UTC, Steve Marks wrote:
>
> Hi All,
>
> Im getting this error on my graylog server, its the latest 1.3.3 release.
>
> Elasticsearch cluster is red. Shards: 40 active, 0 initializing, 0
> relocating, 48 unassigned
>
>
> I have added a new disk and moved the data along with increasing the
> journal size but i cant figure out why this isnt working again, there are
> no errors in the elasticsearch log.
>
> i have no idea where to look or what to do!
>
--
You received this message because you are subscribed to the Google Groups
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/graylog2/ddfc5296-de3b-40b4-87b1-9bafbe700570%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
