admin管理员组

文章数量:1200972

Hi we are using eck operator with 2 nodes cluster in AKS and recently we have updated storageClass so this needs to delete underlying statefulset to take effect. When I am checking cluster health it's in red state.

While checking in k8 pod, statefulset, nodes all are up and running.

When I checked _cluster/allocation/explain I am getting below error

"index": "downsample-5m-.ds-metrics-elasticsearch.stack_monitoring.index_recovery-default-xx",
"can_allocate": "no_valid_shard_copy",
"allocate_explanation": "Elasticsearch can't allocate this shard because there are no copies of its data in the cluster. Elasticsearch will allocate this shard when a node holding a good copy of its data joins the cluster. If no such node is available, restore this index from a recent snapshot."

So, I am assuming by default all index should have primary and replica the why this is not for the above index and how can I resolve this?

本文标签: kibanaError while allocating shards in elasticsearch cloud kubernetesStack Overflow