You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Umesh Kumar Kumawat (Jira)" <ji...@apache.org> on 2025/11/04 08:26:00 UTC

[jira] [Work started] (HBASE-28158) Decouple RIT list management from TRSP invocation

     [ https://issues.apache.org/jira/browse/HBASE-28158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on HBASE-28158 started by Umesh Kumar Kumawat.
---------------------------------------------------
> Decouple RIT list management from TRSP invocation
> -------------------------------------------------
>
>                 Key: HBASE-28158
>                 URL: https://issues.apache.org/jira/browse/HBASE-28158
>             Project: HBase
>          Issue Type: Bug
>          Components: master, Region Assignment
>    Affects Versions: 2.6.0, 2.5.6, 3.0.0-beta-1
>            Reporter: Andrew Kyle Purtell
>            Assignee: Umesh Kumar Kumawat
>            Priority: Major
>              Labels: pull-request-available
>
> Operators bypassed some in progress TRSPs leading to a state where some regions were persistently in transition but hidden. Because the master builds its list of regions in transition by tracking TRSP, the bypass of TRSP removed the regions from the RIT list. 
> Although I can see from reading the code this is the expected behavior, it is surprising for operators and should be changed. Operators expect that regions that should be open but are not appear the master's RIT list, provided by /rits.jsp, the output of the shell's 'rit' command, and in ClusterStatus.
> We should only remove a region from the RIT map when assignment reaches a suitable terminal state.



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