[
https://issues.apache.org/jira/browse/HBASE-20817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527869#comment-16527869
]
Josh Elser commented on HBASE-20817:
------------------------------------
{quote}You can see that there is a log written by WALSplitter about writing max
sequence id file. Could you please enable the DEBUG log to see if there is one
in your cluster?
{quote}
The problem right now is that my cluster is stuck trying to initialize the
master for hours because of all of the MasterProcWALs. I fear that if I start
removing them, I'll either break some assumptions on master procv2
initialization or I'll "fix" the system my making it forget about this RTRP it
needs to finish :)
I did include an {{hdfs dfs -ls}} on the region directory on the other issue
and we don't have anything there (copying for convenience)
{noformat}
ctr-e138-1518143905142-381863-01-000002:/grid/0/log/hbase # hdfs dfs -ls
/apps/hbase/data/data/default/table_izljd/523007f77f96474d01d74ed3d048e173
Found 2 items
-rw-r--r-- 3 hbase hdfs 46 2018-06-27 11:22
/apps/hbase/data/data/default/table_izljd/523007f77f96474d01d74ed3d048e173/.regioninfo
drwxr-xr-x - hbase hdfs 0 2018-06-27 11:22
/apps/hbase/data/data/default/table_izljd/523007f77f96474d01d74ed3d048e173/col_fam_yipdf{noformat}
Sorry I didn't spin out this issue into its own Jira on my own. Got a bit of
tunnel vision :)
> 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
> Reporter: Duo Zhang
> Priority: Blocker
> Fix For: 3.0.0, 2.1.0, 2.0.2, 2.2.0
>
>
> 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)
