Our ES cluster health is often red due to unassigned primary shards.
The unassign.reason for this is "NODE_LEFT" (See details below)
Does this mean that the node left the cluster while it was being assigned the shard?
When the node comes back, how come the unassigned shards are not reassigned back to that node automatically?
curl localhost:9201/_cat/shards?h=index,shard,prirep,state,unassigned.reason,usassigned.for,unassigned.at | grep UNASSIGNED
index1 3 p UNASSIGNED NODE_LEFT 2016-12-12T00:03:36.663Z
index1 3 r UNASSIGNED INDEX_CREATED 2016-12-12T00:01:03.944Z
index1 0 p UNASSIGNED NODE_LEFT 2016-12-12T00:04:59.915Z
index1 0 r UNASSIGNED INDEX_CREATED 2016-12-12T00:01:03.944Z