# RED Status Cluster - UNASSIGNED CLUSTER\_RECOVERED **URL:** \ **Category:** Elasticsearch\ **Created:** [August 8, 2017, 4:14pm UTC](https://discuss.elastic.co/t/red-status-cluster-unassigned-cluster-recovered/96304 "2017-08-08T16:14:52Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ELK\_GB](https://avatars.discourse-cdn.com/v4/letter/e/a9adbd/32.png) [@ELK\_GB](https://discuss.elastic.co/u/ELK_GB)\ **Post date:** [August 8, 2017, 4:14pm UTC](https://discuss.elastic.co/t/red-status-cluster-unassigned-cluster-recovered/96304/1 "2017-08-08T16:14:52Z")
Hi, I have read many resources on red cluster, but I would really appreciate it if someone can tell me what to do here, as I'm stuck at this point not knowing what could work. _\*\*\*Please note I took out cluster status due to permitted number of characters._ ``` Lots of "[0] primary shard is not active Timeout: [1m]" in the logs [root@esclient-1 ~]# curl -XGET ' ******* :9200/_cat/shards?v' index shard prirep state docs store ip node logs-2017.08.02 2 p STARTED 218084 118.3mb 192.12.0.12 esdata-1 logs-2017.08.02 2 r UNASSIGNED logs-2017.08.02 1 p STARTED 217879 118.9mb 192.12.0.12 esdata-1 logs-2017.08.02 1 r UNASSIGNED logs-2017.08.02 3 p STARTED 217081 118.2mb 192.12.0.10 esdata-2 logs-2017.08.02 3 r UNASSIGNED logs-2017.08.02 0 p STARTED 217307 118mb 192.12.0.15 esdata-3 logs-2017.08.02 0 r UNASSIGNED logs-2017.07.24 1 p STARTED 492214 275mb 192.12.0.12 esdata-1 logs-2017.07.24 1 r UNASSIGNED logs-2017.07.24 0 p UNASSIGNED logs-2017.07.24 0 r UNASSIGNED logs-2017.07.17 1 p UNASSIGNED logs-2017.07.17 1 r UNASSIGNED *Truncated* [root@esclient-1 ~]# curl -XGET ' ******* :9200/_cluster/allocation/explain?pretty' { "index" : ".monitoring-logstash-2-2017.08.04", "shard" : 0, "primary" : true, "current_state" : "unassigned", "unassigned_info" : { "reason" : "CLUSTER_RECOVERED", "at" : "2017-08-08T15:19:43.817Z", "last_allocation_status" : "no_valid_shard_copy" }, "can_allocate" : "no_valid_shard_copy", "allocate_explanation" : "cannot allocate because all found copies of the shard are either stale or corrupt", "node_allocation_decisions" : [ { "node_id" : "52Oy-hczTdObNr7HyoGQYg", "node_name" : "esdata-4", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "store" : { "found" : false } }, { "node_id" : "SeMHhljWRpuT76bHNlLqwA", "node_name" : "esdata-3", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "store" : { "in_sync" : false, "allocation_id" : "sBGrm9kmTFKW_ltuNJpDkg" } }, { "node_id" : "c02j74dYSoOgA8KYCzvbWQ", "node_name" : "esdata-1", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "store" : { "found" : false } }, { "node_id" : "i52cA3MGSE2g9Fx92Inrbg", "node_name" : "esdata-2", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "store" : { "in_sync" : false, "allocation_id" : "tQmXydOTTd-cez8A51MZ4A" } } ] } [root@esclient-1 ~]# curl -XGET ' ****** :9200/_cluster/allocation/explain?pretty' { "index" : ".monitoring-data-2", "shard" : 0, "primary" : true, "current_state" : "unassigned", "unassigned_info" : { "reason" : "INDEX_CREATED", "at" : "2017-08-08T15:53:40.175Z", "last_allocation_status" : "no" }, "can_allocate" : "no", "allocate_explanation" : "cannot allocate because allocation is not permitted to any of the nodes", "node_allocation_decisions" : [ { "node_id" : "52Oy-hczTdObNr7HyoGQYg", "node_name" : "esdata-4", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "weight_ranking" : 1, "deciders" : [ { "decider" : "enable", "decision" : "NO", "explanation" : "no allocations are allowed due to {}" } ] }, { "node_id" : "i52cA3MGSE2g9Fx92Inrbg", "node_name" : "esdata-2", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "weight_ranking" : 2, "deciders" : [ { "decider" : "enable", "decision" : "NO", "explanation" : "no allocations are allowed due to {}" } ] }, { "node_id" : "SeMHhljWRpuT76bHNlLqwA", "node_name" : "esdata-3", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "weight_ranking" : 3, "deciders" : [ { "decider" : "enable", "decision" : "NO", "explanation" : "no allocations are allowed due to {}" } ] }, { "node_id" : "c02j74dYSoOgA8KYCzvbWQ", "node_name" : "esdata-1", "transport_address" : " ******* :9300", "node_attributes" : { "ml.enabled" : "true" }, "node_decision" : "no", "weight_ranking" : 4, "deciders" : [ { "decider" : "enable", "decision" : "NO", "explanation" : "no allocations are allowed due to {}" } ] } ] } ``` Move things/reroute one by one ? Or is it possible to do something globally i.e. cluster setting or ES setting to fix all unassigned on once. Can I issue a re-balance , will that help ? ---
**Author:** ![ELK\_GB](https://avatars.discourse-cdn.com/v4/letter/e/a9adbd/32.png) [@ELK\_GB](https://discuss.elastic.co/u/ELK_GB)\ **Post date:** [August 8, 2017, 4:26pm UTC](https://discuss.elastic.co/t/red-status-cluster-unassigned-cluster-recovered/96304/2 "2017-08-08T16:26:17Z")
Here is the cluster health status: ``` [root@esclient-1 ~]# curl -XGET ' ******** :9200/_cluster/health?pretty' { "cluster_name" : " ********", "status" : "red", "timed_out" : false, "number_of_nodes" : 8, "number_of_data_nodes" : 4, "active_primary_shards" : 33, "active_shards" : 33, "relocating_shards" : 0, "initializing_shards" : 0, "unassigned_shards" : 105, "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" : 23.91304347826087 } ``` Used "index.routing.allocation.exclude.\_name": null but I don't see the shard re-allocating. Do I need to restart anything ? Also, used re-route api. The above two will make the explain API skip to the next issue but I dont see the index being allocated anywhere. To minimize the work I have deleted all ".monitoring" old indices as they are not important for us at this point, and many of them are in red status, due to the above. Version is 5.4 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 10, 2017, 8:15am UTC](https://discuss.elastic.co/t/red-status-cluster-unassigned-cluster-recovered/96304/3 "2017-08-10T08:15:39Z")
What version are you on? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 7, 2017, 8:15am UTC](https://discuss.elastic.co/t/red-status-cluster-unassigned-cluster-recovered/96304/4 "2017-09-07T08:15:46Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.