Gabriella Lotz has uploaded this change for review. ( http://gerrit.cloudera.org:8080/25005
Change subject: [auto_rebalancer] enforce per-server move cap ...................................................................... [auto_rebalancer] enforce per-server move cap The auto-rebalancer never enforced its per-server move cap. It budgeted a whole batch at max_moves_per_server * num_tservers and checked moves_per_tserver_, which is empty at selection time, so one batch could pile many moves onto a single server (the most loaded one, which the cap exists to protect). Track per-server move counts within the batch and skip a move once either endpoint reaches the cap. Add MaxMovesPerServerEnforcedWithinOneBatch, which is red before this change: a 6-move batch puts 3 moves on one server with the cap at 1. Change-Id: I9f6b9b200c24d215435329a37e953d75fe923c02 --- M src/kudu/master/auto_rebalancer-test.cc M src/kudu/master/auto_rebalancer.cc 2 files changed, 110 insertions(+), 14 deletions(-) git pull ssh://gerrit.cloudera.org:29418/kudu refs/changes/05/25005/1 -- To view, visit http://gerrit.cloudera.org:8080/25005 To unsubscribe, visit http://gerrit.cloudera.org:8080/settings Gerrit-Project: kudu Gerrit-Branch: master Gerrit-MessageType: newchange Gerrit-Change-Id: I9f6b9b200c24d215435329a37e953d75fe923c02 Gerrit-Change-Number: 25005 Gerrit-PatchSet: 1 Gerrit-Owner: Gabriella Lotz <[email protected]>
