Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.4.17
-
None
-
None
Description
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.