[
https://issues.apache.org/jira/browse/KUDU-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18109354#comment-18109354
]
ASF subversion and git services commented on KUDU-3761:
-------------------------------------------------------
Commit 715d86d880571ba6f3ab028fae2e5b2dabb487f1 in kudu's branch
refs/heads/master from Gabriella Lotz
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=715d86d88 ]
KUDU-3761 prefer follower moves cross-location
LocationBalancingAlgo had no follower awareness: it picked the
first equally most-loaded source in its internal order. Moving a
leader triggers a leadership transfer that can disrupt clients.
Apply the same two-candidate pattern TwoDimensionalGreedyAlgo
uses: among sources tied on load, prefer one that hosts a
non-leader replica of the target table+tag, falling back to any
tied source when none qualifies.
Extend --prefer_follower_replica_moves and
--auto_rebalancing_prefer_follower_replica_moves to cover the
cross-location path too.
Change-Id: I8a162a227071caf37d572ba60c2bc49608d14e65
Reviewed-on: http://gerrit.cloudera.org:8080/24683
Reviewed-by: Ashwani Raina <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
Tested-by: Alexey Serbin <[email protected]>
> Follower preference for LocationBalancingAlgo
> ---------------------------------------------
>
> Key: KUDU-3761
> URL: https://issues.apache.org/jira/browse/KUDU-3761
> Project: Kudu
> Issue Type: Sub-task
> Reporter: Gabriella Lotz
> Assignee: Gabriella Lotz
> Priority: Major
>
> Cross-location moves via {{LocationBalancingAlgo}} have zero follower
> awareness. Fixing this requires:
> 1. Passing {{ts_with_followers_by_table_and_tag}} into
> {{{}LocationBalancingAlgo::GetNextMove(){}}}{{{}, as currently it only
> receives LocationBalancingInfo{}}}
> 2. Applying the same two-candidate (non-leader vs fallback) pattern as
> {{TwoDimensionalGreedyAlgo}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
