HBASE-20476 Open sequence number could go backwards in AssignProcedure

This commit is contained in:
zhangduo 2018-04-27 21:32:03 +08:00
parent 650340abb5
commit 4be96dd8a6
2 changed files with 3 additions and 3 deletions

View File

@ -285,8 +285,9 @@ public class AssignProcedure extends RegionTransitionProcedure {
if (openSeqNum < regionNode.getOpenSeqNum()) {
LOG.warn("Skipping update of open seqnum with " + openSeqNum +
" because current seqnum=" + regionNode.getOpenSeqNum());
} else {
regionNode.setOpenSeqNum(openSeqNum);
}
regionNode.setOpenSeqNum(openSeqNum);
// Leave the state here as OPENING for now. We set it to OPEN in
// REGION_TRANSITION_FINISH section where we do a bunch of checks.
// regionNode.setState(RegionState.State.OPEN, RegionState.State.OPENING);

View File

@ -235,8 +235,7 @@ public abstract class ModifyPeerProcedure extends AbstractPeerProcedure<PeerModi
}
for (Pair<String, Long> name2Barrier : MetaTableAccessor
.getTableEncodedRegionNameAndLastBarrier(conn, tableName)) {
// XXX: for debug only, change to trace after find out the real issues
LOG.debug("Update last pushed sequence id for {}, {}", tableName, name2Barrier);
LOG.trace("Update last pushed sequence id for {}, {}", tableName, name2Barrier);
addToMap(lastSeqIds, name2Barrier.getFirst(), name2Barrier.getSecond().longValue() - 1,
queueStorage);
}