Using elasticsearch for logstash and each morning when the new index is created, the shards are all unassigned. I have to go in and manually assign them with: curl -XPOST -d '{ "commands" : [ { "allocate" : { "index" : "logstash-2016.08.12", "shard" : 4, "node" : "data-node-1", "allow_primary":tru…

All new indexes created have unassigned shards

Topic		Replies	Views
Unassigned shards, v2 Elasticsearch	5	1344	July 6, 2017
Permanent unassigned shards in latest logstash index Elasticsearch	9	698	July 6, 2017
Unassigned Shards Problem Elasticsearch	5	625	July 6, 2017
How to fix UNASSIGNED shard in Elasticsearch Elasticsearch	6	5445	July 5, 2017
Unassigned Shards Elasticsearch	5	471	July 6, 2017

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

All new indexes created have unassigned shards

Related topics