Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-20514 On Master restart if table is stuck in DISABLING state, CLOSED regions should not be considered stuck in-transition 

On startup CLOSED regions of DISABLED and DISABLING tables are treated the same way as not in-transition.
This commit is contained in:
Umesh Agashe 2018-05-01 14:56:24 -07:00 committed by Michael Stack
parent 2e9b96e4f1
commit c4b4023b60
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java
View File

@ -1257,9 +1257,10 @@ public class AssignmentManager implements ServerListener {
} else if (localState == State.OFFLINE || regionInfo.isOffline()) { } else if (localState == State.OFFLINE || regionInfo.isOffline()) {
regionStates.addToOfflineRegions(regionNode); regionStates.addToOfflineRegions(regionNode);
} else if (localState == State.CLOSED && getTableStateManager(). } else if (localState == State.CLOSED && getTableStateManager().
isTableState(regionNode.getTable(), TableState.State.DISABLED)) { isTableState(regionNode.getTable(), TableState.State.DISABLED,
// The region is CLOSED and the table is DISABLED, there is nothing to schedule; TableState.State.DISABLING)) {
// the region is inert. // The region is CLOSED and the table is DISABLED/ DISABLING, there is nothing to
// schedule; the region is inert.
} else { } else {
// These regions should have a procedure in replay // These regions should have a procedure in replay
regionStates.addRegionInTransition(regionNode, null); regionStates.addRegionInTransition(regionNode, null);