hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4739) Master dying while going to close a region can leave it in transition forever
Date Fri, 04 Nov 2011 08:41:00 GMT

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

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

Can we try giving a close call after some timeout.  
Because currently the below code in HRegionServer
{code}
  protected boolean closeRegion(HRegionInfo region, final boolean abort,
      final boolean zk) {
    if (this.regionsInTransitionInRS.containsKey(region.getEncodedNameAsBytes())) {
      LOG.warn("Received close for region we are already opening or closing; " +
          region.getEncodedName());
      return false;
    }
{code}
will prevent a close call reaching once again.  So in the case that J-D had described after
a timeout if we issue a close call he should be able to close the region right?

Correct me if am wrong.
                
> Master dying while going to close a region can leave it in transition forever
> -----------------------------------------------------------------------------
>
>                 Key: HBASE-4739
>                 URL: https://issues.apache.org/jira/browse/HBASE-4739
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Priority: Minor
>             Fix For: 0.92.0, 0.94.0, 0.90.5
>
>
> I saw this in the aftermath of HBASE-4729 on a 0.92 refreshed yesterday, when the master
died it had just created the RIT znode for a region but didn't tell the RS to close it yet.
> When the master restarted it saw the znode and started printing this:
> {quote}
> 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Regions
in transition timed out:  TestTable,0007560564,1320253568406.f76899564cabe7e9857c3aeb526ec9dc.
state=CLOSING, ts=1320253605285, server=sv4r11s38,62003,1320195046948
> 2011-11-03 00:02:49,130 INFO org.apache.hadoop.hbase.master.AssignmentManager: Region
has been CLOSING for too long, this should eventually complete or the server will expire,
doing nothing
> {quote}
> It's never going to happen, and it's blocking balancing.
> I'm marking this as minor since I believe this situation is pretty rare unless you hit
other bugs while trying out stuff to root bugs out.

--
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