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
版权声明:本文标题:kibana - Error while allocating shards in elasticsearch cloud kubernetes? - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1738568639a2100455.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论