hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6169) When a RS aborts without finishing closing a region, this region will always remain "in transition".
Date Wed, 06 Jun 2012 08:59:23 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13290031#comment-13290031
] 

ramkrishna.s.vasudevan commented on HBASE-6169:
-----------------------------------------------

@Maryann
The region close was happening while disabling any table or while balancing? Because while
disabling if this problem happens what you say is possible.  HBASE-5927 we have tried to address
that.  If it is due to some other case then not pretty much sure because if the RIT is in
PENDING_CLOSE I thought we are handling it?(Need to check)
Which version of HBASE you found this issue?
                
> When a RS aborts without finishing closing a region, this region will always remain "in
transition".
> ----------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6169
>                 URL: https://issues.apache.org/jira/browse/HBASE-6169
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.6, 0.94.0
>            Reporter: Maryann Xue
>
> When RS got an ZK error when trying to create a "CLOSING" node in the process of closing
a region, it hence aborts without completing closing of the region.
> RS is then discovered dead by HMaster. ServerShutdownHandler does not try to reassign
this region for it is in PENDING_CLOSE state; while all regions that originally belong to
the dead RS get removed from the "regions" map.
> TimeoutMonitor then endlessly tries to "unassign" this region with LOG message "Region
has been PENDING_CLOSE for too long". The "unassign" returns without doing anything, for this
region does not exist in the "regions" map:
>   public void unassign(HRegionInfo region, boolean force, ServerName dest) {
>     // TODO: Method needs refactoring.  Ugly buried returns throughout.  Beware!
>     LOG.debug("Starting unassignment of region " +
>       region.getRegionNameAsString() + " (offlining)");
>     synchronized (this.regions) {
>       // Check if this region is currently assigned
>       if (!regions.containsKey(region)) {
>         LOG.debug("Attempted to unassign region " +
>           region.getRegionNameAsString() + " but it is not " +
>           "currently assigned anywhere");
>         return;
>       }
>     }
>   ...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message