[jira] [Commented] (KUDU-3732) Get consensus state from CatalogManager

["Gabriella Lotz (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18078986#comment-18078986 ] 

Gabriella Lotz commented on KUDU-3732:
--------------------------------------

WIth [https://gerrit.cloudera.org/c/24191/] merged, first TODO has been addressed.

> Get consensus state from CatalogManager
> ---------------------------------------
>
>                 Key: KUDU-3732
>                 URL: https://issues.apache.org/jira/browse/KUDU-3732
>             Project: Kudu
>          Issue Type: Sub-task
>            Reporter: Gabriella Lotz
>            Assignee: Gabriella Lotz
>            Priority: Major
>
> h2. Address the two existing TODOs
> Both are in {{{}[src/kudu/master/auto_rebalancer.cc](src/kudu/master/auto_rebalancer.cc){}}}:
> {*}TODO 1 (line 478){*}: {{remove moves that fail to be scheduled from 'replica_moves'}}
> Currently {{ExecuteMoves()}} iterates all moves but does not remove failed-to-schedule moves. Failed moves stay in the in-progress set, blocking future rounds from reconsidering those tablets. Fix: collect scheduling failures and erase them from {{replica_moves}} before returning, so {{CheckReplicaMovesCompleted}} only waits on actually-submitted moves.
> {*}TODO 2 (line 853){*}: {{Retrieve consensus state from CatalogManager instead}}
> {{CheckMoveCompleted()}} currently mirrors the tool-side {{CheckCompleteMove()}} — it issues RPCs. The better path reads consensus state from the master's in-memory catalog (already available via {{{}CatalogManager{}}}), eliminating the extra RPC round-trip per move. The implementation pattern exists in {{{}CatalogManager::GetTabletLocations{}}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)