information about existing shard data is still being retrieved from some of the nodes
Elasticsearch | 作者 lsyff123 | 发布于2020年06月08日 | 阅读数：3760
网络闪断，节点脱离集群，恢复之后，有部分replica一直是unassigned，无法恢复。有哪位大佬遇见过。
具体报错信息如下：
"shard": 5,
"primary": false,
"current_state": "unassigned",
"unassigned_info": {
"reason": "NODE_LEFT",
"at": "2020-06-08T01:57:10.292Z",
"details": "node_left [d6kvXUvQS62aBozI8Od2Fw]",
"last_allocation_status": "no_attempt"
},
"can_allocate": "awaiting_info",
"allocate_explanation": "cannot allocate because information about existing shard data is still being retrieved from some of the nodes",
具体报错信息如下：
"shard": 5,
"primary": false,
"current_state": "unassigned",
"unassigned_info": {
"reason": "NODE_LEFT",
"at": "2020-06-08T01:57:10.292Z",
"details": "node_left [d6kvXUvQS62aBozI8Od2Fw]",
"last_allocation_status": "no_attempt"
},
"can_allocate": "awaiting_info",
"allocate_explanation": "cannot allocate because information about existing shard data is still being retrieved from some of the nodes",
2 个回复
byx313 - BLOG:https://www.jianshu.com/u/43fd06f9589c
赞同来自:
shard5的副本应该是正在同步数据
lsyff123
赞同来自:
POST /_cluster/reroute
{
"commands": [
{
"allocate_replica": {
"index": "index_name",
"shard": 6,
"node": "Node_name"
}
}
]
}