You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the excellent _cluster/reroute?explain API gives very detailed information about why a particular shard could or couldn't be moved, but we have little insight into why a cluster doesn't rebalance shards automatically.
eg if you change a setting like cluster.routing.allocation.balance.primary, and nothing changes, it is difficult to know why nothing has changed.
It would be very useful to have more insight into the decisions made by each allocation decider for each shard.
The text was updated successfully, but these errors were encountered:
Sometimes I find that the allocation decider has to be "kicked" by manually forcing a move. I'm not sure what the deal is there but something like this could help debug that.
Currently, the excellent
_cluster/reroute?explain
API gives very detailed information about why a particular shard could or couldn't be moved, but we have little insight into why a cluster doesn't rebalance shards automatically.eg if you change a setting like
cluster.routing.allocation.balance.primary
, and nothing changes, it is difficult to know why nothing has changed.It would be very useful to have more insight into the decisions made by each allocation decider for each shard.
The text was updated successfully, but these errors were encountered: