You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (Jira)" <ji...@apache.org> on 2025/03/31 10:07:00 UTC

[jira] [Resolved] (HBASE-29206) RollingBatchSuspendResumeRsAction can not actually 'resume' a region server

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

Duo Zhang resolved HBASE-29206.
-------------------------------
    Fix Version/s: 2.7.0
                   3.0.0-beta-2
     Hadoop Flags: Reviewed
       Resolution: Fixed

Pushed to branch-2+. Thanks [~stoty] for reviewing!

> RollingBatchSuspendResumeRsAction can not actually 'resume' a region server
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-29206
>                 URL: https://issues.apache.org/jira/browse/HBASE-29206
>             Project: HBase
>          Issue Type: Improvement
>          Components: integration tests
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.7.0, 3.0.0-beta-2
>
>
> After HBASE-28023, we can successfully suspend and resume the region servers, but the problem is that usually after resuming, the region server will receive a YouAreDeadException while calling reportForDuty and also the zk session will expire, so soon the region server will abort.
> A possible way is to use autostart, so the region server will restart automatically, but the problem is that, we also have some restart actions in our integration tests, they use 'start' instead of 'autostart', so even if we use autostart, after a BatchRestartRsAction we will fallback to start and cause problem when a RollingBatchSuspendResumeRsAction comes.



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