One of my node down accidently, and it joined cluster few minutes later.
After that To allocate shard faster, I changed 'cluster.routing.allocation.node_concurrent_incoming_recoveries' 10 to 50
And below issue happened.
Can you give me solution?
{
"note" : "No shard was specified in the explain API request, so this response explains a randomly chosen unassigned shard. There may be other unassigned shards in this cluster which cannot be assigned for different reasons. It may not be possible to assign this shard until one of the other shards is assigned correctly. To explain the allocation of other shards (whether assigned or unassigned) you must specify the target shard in the request to this API.",
"index" : "somelog-2023.02.22-000240",
"shard" : 4,
"primary" : false,
"current_state" : "unassigned",
"unassigned_info" : {
"reason" : "NODE_LEFT",
"at" : "2023-03-14T02:21:08.147Z",
"details" : "node_left [jDuYFVrSTX-8lyMH6xu4iA]",
"last_allocation_status" : "no_attempt"
},
"can_allocate" : "throttled",
"allocate_explanation" : "allocation temporarily throttled",
"node_allocation_decisions" : [
{
"node_id" : "LqEyEd8VTrm2Mq9xwdl0Lw",
"node_name" : "node1",
"transport_address" : "ip:port",
"node_attributes" : {
"data" : "warm",
"xpack.installed" : "true",
"transform.node" : "true"
},
"node_decision" : "throttled",
"deciders" : [
{
"decider" : "throttling",
"decision" : "THROTTLE",
"explanation" : "reached the limit of outgoing shard recoveries [50] on the node [qFv22aI5SgKVMt0PX67Ulg] which holds the primary, cluster setting [cluster.routing.allocation.node_concurrent_outgoing_recoveries=10] (can also be set via [cluster.routing.allocation.node_concurrent_recoveries])"
}
]
},