[
https://issues.apache.org/jira/browse/HBASE-28139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17773533#comment-17773533
]
ruanhui commented on HBASE-28139:
---------------------------------
Thanks for the quick reply [~saber_li]
So this is an improvement based on
https://issues.apache.org/jira/browse/HBASE-23636 ? It is not enough to just
check whether the table's status is DISABLEING ? I have a question about the
patch, why the TransitionType is ASSIGN instead of UNASSIGN in the line 14 ?
Would you mind explaining it a little more ?
Thanks.
> Disable table may hang when SCP create TRSP but DTP didn't set tableState to
> disabling
> --------------------------------------------------------------------------------------
>
> Key: HBASE-28139
> URL: https://issues.apache.org/jira/browse/HBASE-28139
> Project: HBase
> Issue Type: Bug
> Components: amv2
> Affects Versions: 2.4.17
> Reporter: Li Chao
> Priority: Major
> Attachments: HBASE-28139.patch
>
>
> Consider the following case：
> 1. RegionServer stop or abort, ServerCrashProcedure start running;
> 2. Now, DisableTableProcedure start running but not set tableState to
> disabling;
> 3. ServerCrashProcedure create TransitStateProcedure with success, but can
> not running because of xLock had hold by DisableTableProcedure ;
> 4. DisableTable Procedure UnassignProcedure RPC fails because server is down.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
