You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/11 19:53:00 UTC

[jira] [Resolved] (HBASE-20728) Failure and recovery of all RSes in a RSgroup requires master restart for region assignments

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

Andrew Kyle Purtell resolved HBASE-20728.
-----------------------------------------
      Assignee:     (was: Sakthi)
    Resolution: Incomplete

> Failure and recovery of all RSes in a RSgroup requires master restart for region assignments
> --------------------------------------------------------------------------------------------
>
>                 Key: HBASE-20728
>                 URL: https://issues.apache.org/jira/browse/HBASE-20728
>             Project: HBase
>          Issue Type: Bug
>          Components: master, rsgroup
>            Reporter: Biju Nair
>            Priority: Minor
>
> If all the RSes in a RSgroup hosting user tables fail and recover, master still looks for old RSes (with old timestamp in the RS identifier) to assign regions. i.e. Regions are left in transition making the tables in the RSGroup unavailable. User need to restart {{master}} or manually assign the regions to make the tables available. Steps to recreate the scenario in a local cluster
>  - Add required properties to {{site.xml}} to enable {{rsgroup}} and start hbase
>  - Bring up multiple region servers using {{local-regionservers.sh start}}
>  - Create a {{rsgroup}} and move a subset of  {{regionservers}} to the group
>  - Create a table, move it to the group and put some data
>  - Stop the {{regionservers}} in the group and restart them
>  - From the {{master UI}}, we can see that the region for the table in transition and the RS name in the {{RIT}} message has the old timestamp.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)