[
https://issues.apache.org/jira/browse/HBASE-26283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417275#comment-17417275
]
bolao commented on HBASE-26283:
-------------------------------
thanks for you replay! we tired the flowing points.
1. our jdk version is 8u291, and we note that JDK-8215355 has been repaired in
8u251. maybe it's not jdk bug.
2. we check our log again, but there is still no useful information. Due to the
particularity of the work, we only get master log, then hbase cluster be
repaired by maintainers through hbck tools, so we can't get more information
about that time. (we have upload compressed master log)
3. we also see the source
code(https://github.com/apache/hbase/blob/fd3fdc08d1cd43eb3432a1a70d31c3aece6ecabe/hbase-server/src/main/java/org/apache/hadoop/hbase/master/assignment/AssignmentManager.java#L616)
it's will be create TRSP when the override is set to true. maybe maintainers
used hbck tool with param is true, then restart. Is it possible to load two
procedure from master:store or wal?
thanks!
> RegionServer ignored a procedure dute to repeatedly opening which lead region
> stuck in RIT
> ------------------------------------------------------------------------------------------
>
> Key: HBASE-26283
> URL: https://issues.apache.org/jira/browse/HBASE-26283
> Project: HBase
> Issue Type: Improvement
> Components: Region Assignment
> Affects Versions: 2.3.5
> Reporter: bolao
> Priority: Minor
>
> when hbase cluster shut down Suddenlly, there are some repeatedly
> opening regions and cause them to stuck in RTI。we found
> org.apache.hadoop.hbase.regionserver.handler.AssignRegionHandler#process()
> directly return when handle repeatedly opening regions， and don't report to
> master, master unable to process next status for this procedure， and
> regions stuck in RIT。so can we do like this:
> # AssignRegionHandler report the region is online if regionserver found the
> region is online,
> # or AssignRegionHandler report the region is failed online if regionserver
> found the region is online, let Hmater to retry。
> please give some suggestions, thanks !
> {code:java}
> // code placeholder
> Region onlineRegion = rs.getRegion(encodedName); if (onlineRegion != null) {
> LOG.warn("Received OPEN for the region:{}, which is already online",
> regionName);
> // Just follow the old behavior, do we need to call
> reportRegionStateTransition? Maybe not?
> // For normal case, it could happen that the rpc call to schedule this
> handler is succeeded,
> // but before returning to master the connection is broken. And when master
> tries again, we
> // have already finished the opening. For this case we do not need to call
> // reportRegionStateTransition any more.
> return; }
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
