Bulk Operation

HBASE-20828 Ignore the reportRegionStateTransition call from a dead server

HBASE-20828 WALProcedure may remove proc wal files still with active procedures

HBASE-20828 Backport "HBASE-21463 The checkOnlineRegionsReport can accidentally complete a TRSP" to branch-2.1 and branch-2.0

HBASE-20828 Should not persist the dispatched field for RegionRemoteProcedureBase

HBASE-20828 Add more comments about how we do fencing for WALProcedureStore

HBASE-20828 Retry on reportRegionStateTransition can lead to unexpected errors

HBASE-20828 The checkOnlineRegionsReport can accidentally complete a TRSP

HBASE-20828 Procedures for meta table/region should be able to execute in separate workers

HBASE-20828 Do not kill RS if reportOnlineRegions fails

HBASE-20828 Abort split/merge procedure if there is a table procedure of the same table going on

HBASE-20828 Procedure with holdlock=false should not be restored lock when restarts

HBASE-20828 Add debug log for procedure stack id related operations

HBASE-20828 Add some verbose log to MasterProcedureScheduler

HBASE-20828 Revisit the lock and queue implementation in MasterProcedureScheduler

HBASE-20828 Procedure holds the lock should put to front of the queue after restart

HBASE-20828 Rewrite the buildingHoldCleanupTracker method in WALProcedureStore

HBASE-20828 Procedure may be deleted improperly during master restarts resulting in 'Corrupt'

HBASE-20828 Polish the rollback implementation in ProcedureExecutor

HBASE-20828 The force update thread may have race with PE worker when the procedure is rolling back

HBASE-20828 Simplify the implementation of WALProcedureMap

HBASE-20828 ReopenTableRegionsProcedure will enter an infinite loop if we schedule a TRSP at the same time

HBASE-20828 Should not skip force updating for a sub procedure even if it has been finished

HBASE-20828 Backport HBASE-21278 to branch-2.1 and branch-2.0

HBASE-20828 The getActiveMinProcId and getActiveMaxProcId of BitSetNode are incorrect if there are no active procedure

HBASE-20828 The implementation of BitSetNode is not efficient

HBASE-20828 TransitRegionStateProcedure should not fail with FAILED_OPEN when acting as a sub procedure

HBASE-20828 HostingServer in UnassignProcedure is not accurate

HBASE-20828 Do not rollback successful sub procedures when rolling back a procedure

HBASE-20828 Add more tests for procedure store related classes

HBASE-20828 Need to find a way to limit the number of proc wal files

HBASE-20828 Refactor WALProcedureStore and add more comments for better understanding the implementation

HBASE-20828 Add jitter for ProcedureUtil.getBackoffTimeMs

HBASE-20828 Skip persistence when retrying for assignment related procedures

HBASE-20828 Use CompatRemoteProcedureResolver to dispatch open/close region requests to RS

HBASE-20828 Load procedure wals with multiple threads

HBASE-20828 Rename the closed procedure wal files so that we do not need to call recoverLease when restarting

HBASE-20828 Allow the procedure implementation to skip persistence of the state after a execution

HBASE-20828 Implement exponential retrying backoff for Assign/UnassignRegionHandler introduced in HBASE-21217

HBASE-20828 Revisit the close region related code at RS side

HBASE-20828 Revisit the executeProcedure method for open/close region

HBASE-20828 Race in region opening and load balancing can cause region stuck in RIT

HBASE-20828 Reimplement the retry backoff logic for ReopenTableRegionsProcedure

HBASE-20828 ReopenTableRegionsProcedure sometimes hangs

HBASE-20828 The timeout retry logic for several procedures are broken after master restarts

HBASE-20828 Remove the explicit timeout config for TestTruncateTableProcedure

HBASE-20828 Move TestCreateTableProcedure.testMRegions to a separated file

HBASE-20828 Adding getter methods to some private fields in ProcedureV2 module

HBASE-20828 Introduce a mechanism to bypass the execution of a stuck procedure

HBASE-20828 Reimplement assign/unassign related procedure metrics

HBASE-20828 Confirm that we can (rolling) upgrade from 2.0.x and 2.1.x to 2.2.x after HBASE-20881

HBASE-20828 Possible NPE if ModifyTable and region split happen at the same time

HBASE-20828 Exclusive lock may be held by a SUCCESS state procedure forever

HBASE-20828 Procedure worker should not quit when getting unexpected error

HBASE-20828 Meta Table should be able to online even if all procedures are lost

HBASE-20828 Add cache for TableStateManager

HBASE-20828 Revisit the expected states for open/close

HBASE-20828 Find another way to test the backoff mechanism in TRSP

HBASE-20828 One operation in procedure batch throws an exception will cause all RegionTransitionProcedures receive the same exception

HBASE-20828 SCP can be scheduled multiple times for the same RS

HBASE-20828 Lock may not be taken or released while rolling back procedure

HBASE-20828 ArrayIndexOutOfBoundsException when rolling back procedure

HBASE-20828 Split/Merge table can be executed concurrently with DisableTableProcedure

HBASE-20828 There will be race when we call suspendIfNotReady and then throw ProcedureSuspendedException

HBASE-20828 Possible NPE in ReopenTableRegionsProcedure

HBASE-20828 Merge the update procedure store on locking with the general persist after a procedure execution

HBASE-20828 Data loss if splitting region while ServerCrashProcedure executing

HBASE-20828 Introduce a region transition procedure to handle all the state transition for a region

HBASE-20828 Data loss if merging regions while ServerCrashProcedure executing

HBASE-20828 RS may get killed while master restarts

HBASE-20828 RS was killed due to master thought the region should be on a already dead server

HBASE-20828 Merged region's RIT state may not be cleaned after master restart

HBASE-20828 The parent procedure of RegionTransitionProcedure may not have the table lock

HBASE-20828 Restore procedure locks when master restarts

HBASE-20828 Handle null states in AM