[
https://issues.apache.org/jira/browse/HBASE-20476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16456180#comment-16456180
]
Duo Zhang commented on HBASE-20476:
-----------------------------------
OK I think the problem is here
{noformat}
2018-04-27 08:59:30,989 DEBUG
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=33421]
assignment.RegionTransitionProcedure(230): Received report OPENED seqId=0,
pid=93, ppid=45, state=RUNNABLE:REGION_TRANSITION_FINISH; AssignProcedure
table=test, region=081d9e29e93559a82f8d7992c782311d,
target=asf911.gq1.ygridcore.net,35259,1524819543873; rit=OPENING,
location=asf911.gq1.ygridcore.net,35259,1524819543873
2018-04-27 08:59:30,989 WARN
[RpcServer.default.FPBQ.Fifo.handler=3,queue=0,port=33421]
assignment.AssignProcedure(286): Skipping update of open seqnum with 0 because
current seqnum=5
{noformat}
In the log we say that we will skip updating but actually we do not skip...
{code}
if (openSeqNum < regionNode.getOpenSeqNum()) {
LOG.warn("Skipping update of open seqnum with " + openSeqNum +
" because current seqnum=" + regionNode.getOpenSeqNum());
}
regionNode.setOpenSeqNum(openSeqNum);
{code}
Not sure if adding a simple break could fix the problem. Let me add a new
Exception() here to see where is the zero openSeqNum from.
[~stack] This maybe a serious problem sir. I do not think there is much
difference between the AMv2 code of master/branch-2 and branch-2.0.
> Fix the flaky TestReplicationSmallTests unit test
> -------------------------------------------------
>
> Key: HBASE-20476
> URL: https://issues.apache.org/jira/browse/HBASE-20476
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Duo Zhang
> Priority: Major
> Attachments: HBASE-20476-addlog.patch, HBASE-20476.patch
>
>
> See
> https://builds.apache.org/job/HBASE-Find-Flaky-Tests/lastSuccessfulBuild/artifact/dashboard.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
