You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/06/20 08:40:00 UTC
[jira] [Commented] (HBASE-20752) Make sure the regions are truly
reopened after ReopenTableRegionsProcedure
[ https://issues.apache.org/jira/browse/HBASE-20752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517922#comment-16517922 ]
Duo Zhang commented on HBASE-20752:
-----------------------------------
The patch is ready but when testing I found that a region in OPEN state could have a -1 openSeqNum in the RegionStateNode, this is a bit strange. Digging.
> Make sure the regions are truly reopened after ReopenTableRegionsProcedure
> --------------------------------------------------------------------------
>
> Key: HBASE-20752
> URL: https://issues.apache.org/jira/browse/HBASE-20752
> Project: HBase
> Issue Type: Bug
> Reporter: Duo Zhang
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
>
> The MRP may fail due to some reason, so we need to add some checks in ReopenTableRegionsProcedure, if we fail to reopen a region, then we should schedule a new MRP for it again.
> And a future improvement maybe that, we can introduce a new type of procedure to reopen a region, where we just need a simple call to RS, and do not need to unassign it and assign it again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)