你不会是程序猿吧?

unassigned_shards一直无法分配, number_of_in_flight_fetch 过高,

Elasticsearch | 作者 lsyff123 | 发布于2020年06月18日 | 阅读数:130

cluster health显示  unassigned_shards 一直无法分配,  "number_of_in_flight_fetch": 1080 较高且一直没有变化
 
{
"cluster_name": "ESNewMedia",
"status": "red",
"timed_out": false,
"number_of_nodes": 57,
"number_of_data_nodes": 53,
"active_primary_shards": 26214,
"active_shards": 45251,
"relocating_shards": 0,
"initializing_shards": 0,
"unassigned_shards": 374,
"delayed_unassigned_shards": 0,
"number_of_pending_tasks": 0,
"number_of_in_flight_fetch": 1080,
"task_max_waiting_in_queue_millis": 0,
"active_shards_percent_as_number": 99.18027397260273
}
explain显示可以分配
"index": "sj_shrink",
"shard": 0,
"primary": true,
"current_state": "unassigned",
"unassigned_info": {
"reason": "NODE_LEFT",
"at": "2020-06-18T07:42:51.849Z",
"details": "node_left [vszUScqBQ0OeZZH9LA9p-w]",
"last_allocation_status": "awaiting_info"
},
"can_allocate": "yes",
"allocate_explanation": "can allocate the shard",
已邀请:

tacsklet - 公司有用到es

赞同来自:

NODE_LEFT是有些节点脱离集群了,上面的索引就会显示为未分配。
你看看是不是有些节点有问题,然后里面还是包含的主分片。

要回复问题请先登录注册