[
https://issues.apache.org/jira/browse/HBASE-20817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529306#comment-16529306
]
Ankit Singhal commented on HBASE-20817:
---------------------------------------
bq. Hey Josh Elser, is this your case? Read only table?
[~Apache9], Josh is on holiday so not sure if he will access his mailbox for
next couple of days. but from his last comments, it seems we are talking about
the same tables(table_xxxxx) created by Atlas/Titan.
{code}
2018-06-27 17:16:25,270 INFO [PEWorker-16] procedure2.ProcedureExecutor:
Finished subprocedure(s) of pid=15024, ppid=15023,
state=RUNNABLE:REOPEN_TABLE_REGIONS_CONFIRM_REOPENED;
ReopenTableRegionsProcedure table=table_izljd; resume parent processing.
2018-06-27 17:16:25,270 INFO [PEWorker-16] procedure2.ProcedureExecutor:
Finished pid=320739, ppid=15024, state=SUCCESS; MoveRegionProcedure
hri=523007f77f96474d01d74ed3d048e173,
source=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688,
destination=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688
in 497msec
2018-06-27 17:16:25,279 INFO [PEWorker-2] procedure2.ProcedureExecutor:
Initialized subprocedures=[{pid=320742, ppid=15024,
state=RUNNABLE:MOVE_REGION_UNASSIGN; MoveRegionProcedure
hri=523007f77f96474d01d74ed3d048e173,
source=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688,
destination=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688}]
2018-06-27 17:16:25,291 INFO [PEWorker-2] procedure.MasterProcedureScheduler:
pid=320742, ppid=15024, state=RUNNABLE:MOVE_REGION_UNASSIGN;
MoveRegionProcedure hri=523007f77f96474d01d74ed3d048e173,
source=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688,
destination=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688
checking lock on 523007f77f96474d01d74ed3d048e173
2018-06-27 17:16:25,291 INFO [PEWorker-2] procedure2.ProcedureExecutor:
Initialized subprocedures=[{pid=320743, ppid=320742,
state=RUNNABLE:REGION_TRANSITION_DISPATCH; UnassignProcedure table=table_izljd,
region=523007f77f96474d01d74ed3d048e173,
server=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688}]
2018-06-27 17:16:25,292 INFO [PEWorker-2] procedure.MasterProcedureScheduler:
pid=320743, ppid=320742, state=RUNNABLE:REGION_TRANSITION_DISPATCH;
UnassignProcedure table=table_izljd, region=523007f77f96474d01d74ed3d048e173,
server=ctr-e138-1518143905142-381863-01-000002.hwx.site,16020,1530113920688
checking lock on 523007f77f96474d01d74ed3d048e173
2018-06-27 17:16:25,292 INFO [PEWorker-2] assignment.RegionStateStore:
pid=320743 updating hbase:meta row=523007f77f96474d01d74ed3d048e173,
regionState=CLOSING
{code}
> Infinite loop when executing ReopenTableRegionsProcedure
> ---------------------------------------------------------
>
> Key: HBASE-20817
> URL: https://issues.apache.org/jira/browse/HBASE-20817
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
> Attachments: HBASE-20817.patch
>
>
> As discussed in HBASE-20792, it seems that a region's openSeqNum could remain
> the same after a sucessful reopen, which causes the RTRP loop infinitely.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
