标签：name over 硬盘 recovery comm status local close prim
今天ES 服务器，一致处于yellow状态，有节点带分配，看了一下ES的日志，发现LockObtainFailedException 异常，在网上看到解决方案，先close 再open，可以 解决，试了，没用。 无奈重启服务器（非线上），依然相同的错误， 无奈使出杀手锏，手动分配，curl -XPOST ‘localhost:9200/_cluster/reroute‘ -d ‘{
"commands" : [ {
"allocate" : {
"index" : “indexname",
"shard" : 2,
"node" : "p7hX9aD3STuGUHR-R03UPA",
"allow_primary" : true
}
}
]
}‘真正的问题显现出来，
[YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(node passes include/exclude/require filters)][YES(below shard recovery limit of [2])][YES(allocation disabling is ignored)][NO(more than allowed [85.0%] used disk on node, free: [12.726023442766103%])]"},"status":400}
原来是硬盘不够了，哎！ 删除日志，问题解决。
ES LockObtainFailedException Can‘t lock shard 处理
标签：name over 硬盘 recovery comm status local close prim
原文地址：http://blog.51cto.com/12597095/2318976
