Hello, I came to work from my holidays today and have some troubles with my shards. > { > "cluster_name" : "elasticsearch", > "status" : "yellow", > "timed_out" : false, > "number_of_nodes" : 5, > "number_of_data_nodes" : 4, > "active_primary_shards" : 5535, > "active_shards" …

I found the problem my diskspace-watermark was too low. How can I reduce it? I can't change the number shards once they are configured, if I remember it correct.

Discuss the Elastic Stack

Problem with unassigned Shards

Elastic Stack Elasticsearch

warkolm (Mark Walkom) January 9, 2017, 7:48am 5

If you are on 5+ you can use _shrink.

Topic		Replies	Views
Elastic Search Cluster has unassigned Shards Elasticsearch	4	3325	May 25, 2017
Unassigned Shards, what to do about it Elasticsearch	13	7460	August 28, 2019
Unassigned shards allocation Elasticsearch	6	1506	July 5, 2017
Unassigned shards Elasticsearch	3	522	July 6, 2017
Shards UNASSIGNED even tho they exist on disk Elasticsearch	2	554	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.

Problem with unassigned Shards

Related topics