Shard Siem cause cluster red

Elastic Stack Elasticsearch
1

Hello everyone,

I have a problem with my .siem-signals-default index. The shard goes to red status and I can't reallocate the shard to another node. Because the shard seems to not be in my cluster and I can't get it back. See the message below:

"index" : ".siem-signals-default-000003",
  "shard" : 0,
  "primary" : true,
  "current_state" : "unassigned",
  "unassigned_info" : {
    "reason" : "CLUSTER_RECOVERED",
    "at" : "2021-12-15T10:17:49.049Z",
    "last_allocation_status" : "no_valid_shard_copy"
  },
  "can_allocate" : "no_valid_shard_copy",
  "allocate_explanation" : "cannot allocate because a previous copy of the primary shard existed but can no longer be found on the nodes in the cluster",

Has anyone encountered this problem? Or can someone tell me how to solve it?

Thanks a lot !

2

Welcome to our community! :smiley:

What is the output from the _cluster/stats?pretty&human API?

3

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