Hi I have a elasticsearch service running on one node. After I restart the ES. Some shard remain unassigned. [sflow@ES01 bin]$ curl -XGET 'ES01:9200/_cat/shards?pretty' sflow_51452355200 3 p STARTED 1000660 414.3mb 10.79.148.184 ES01 sflow_51452355200 4 p STARTED 1000123 414.2mb 10.79.…

After I restart ES, some shard remain unassigned

nik9000 (Nik Everett) March 18, 2016, 3:19pm 4

Transaction log replay, probably.

Topic		Replies	Views
Lost data after restarting ES Elasticsearch	1	414	July 6, 2017
After restarting ElasticSearch, a lot of shards unassigned Elasticsearch	1	1097	July 5, 2017
Shards unassigned after elasticsearch restart Elasticsearch	16	3418	September 5, 2017
Elasticsearch restart leave unassigned shards Elasticsearch	2	430	July 6, 2017
SOLVED: Unassigned shards after restart, allocated for local recovery, should exist but doesn't + no segments file found in store Elasticsearch	2	4196	July 5, 2017