All shrads in Unassigned state

Elastic Stack Elasticsearch
1

Hi,

I have an elastic cluster of 3 data nodes,3 masters and 3 clients.
curl -v -u admin http://localhost:9200/_cluster/health?pretty --noproxy '*'

{
"cluster_name" : "myesdb",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 9,
"number_of_data_nodes" : 3,
"active_primary_shards" : 0,
"active_shards" : 0,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 75,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 0.0
}
I attached 1GB volume to each of datanodes. The volumes are full and all shards are found in unassigned state( curl --noproxy '*' -v -u admin -XGET 'http://localhost:9200/_cat/shards'
I created new volumes and restarted the nodes, but still the cluster is in state red and all nodes are still in unassigned state.

I tried with the following settings, but still the shards are not re-balanced and the cluster is in status red. How can I solve the unassigned shard problem?

"cluster.routing.allocation.allow_rebalance" : "always",
"cluster.routing.allocation.cluster_concurrent_rebalance" : 10
"cluster.routing.rebalance.enable" : "all"

2

So you removed the existing data volumes and added new ones?

If that is the case, then you will never be able to assign those shards as the data is lost.

3

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.