Shards Allocation problem

Elastic Stack Elasticsearch
1

If I try to allocate my shards, i get this message. Any solution?

{
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "[move_allocation] can't move [logstash-2017.04.18][5], from {logstash1}{WQw8TaAuTH6sQCp4BUPWKA}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, to {logstash2}{S0tO6YGqTDmLdxAujsJnPQ}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, since its not allowed, reason: [YES(no snapshots are currently running)][YES(allocation disabling is ignored)][YES(target node version [2.4.1] is same or newer than source node version [2.4.1])][YES(shard is not allocated to same node or host)][YES(shard is primary)][YES(no allocation awareness enabled)][YES(below shard recovery limit of [2])][YES(node passes include/exclude/require filters)][YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(allocation disabling is ignored)][NO(after allocation less than required [800gb] free on node, free: [947.2gb])]"
}
],
"type": "illegal_argument_exception",
"reason": "[move_allocation] can't move [logstash-2017.04.18][5], from {logstash1}{WQw8TaAuTH6sQCp4BUPWKA}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, to {logstash2}{S0tO6YGqTDmLdxAujsJnPQ}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, since its not allowed, reason: [YES(no snapshots are currently running)][YES(allocation disabling is ignored)][YES(target node version [2.4.1] is same or newer than source node version [2.4.1])][YES(shard is not allocated to same node or host)][YES(shard is primary)][YES(no allocation awareness enabled)][YES(below shard recovery limit of [2])][YES(node passes include/exclude/require filters)][YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(allocation disabling is ignored)][NO(after allocation less than required [800gb] free on node, free: [947.2gb])]"
},
"status": 400
}

2

Looks like you need more disk space.

3

I changed some config params, and now the node1 and node2 running fine but the node3 don't. I compared the configs but there is no diff just node name...

{
"error": {
"root_cause": [
{
"type": "remote_transport_exception",
"reason": "[logstash2][xxx.xxx.xxx.xxx:9300][cluster:admin/reroute]"
}
],
"type": "illegal_argument_exception",
"reason": "[move_allocation] can't move [logstash-2017.04.18][4], from {ccb_logstash1}{tyamrv7MQA-v98_5zTSVEQ}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, to {ccb_logstash3}{A0zlcY7-TXOP4uO7zAZdSg}{xxx.xxx.xxx.xxx}{xxx.xxx.xxx.xxx:9300}{max_local_storage_nodes=1, master=true}, since its not allowed, reason: [YES(no snapshots are currently running)][YES(allocation disabling is ignored)][YES(target node version [2.4.1] is same or newer than source node version [2.4.1])][YES(shard is not allocated to same node or host)][YES(shard is primary)][YES(no allocation awareness enabled)][YES(below shard recovery limit of [2])][YES(node passes include/exclude/require filters)][YES(total shard limit disabled: [index: -1, cluster: -1] <= 0)][YES(allocation disabling is ignored)][NO(after allocation less than required [50gb] free on node, free: [870.8gb])]"
},
"status": 400
}

i can't understand the strong marked -1.

4

Still a disk issue.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.