hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-20) Regions getting messages from master to MSG_REGION_CLOSE_WITHOUT_REPORT
Date Wed, 23 Apr 2008 22:51:21 GMT

     [ https://issues.apache.org/jira/browse/HBASE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-20:

    Fix Version/s: 0.2.0

I think this issue can be resolved for 0.2.0.  A bunch of stuff has been done to assuage thrashing
on startup (having regionservers send heartbeat while region is being opened, balancing of
regions across cluster).  Verify this is no longer an issue and then close.

> Regions getting messages from master to MSG_REGION_CLOSE_WITHOUT_REPORT
> -----------------------------------------------------------------------
>                 Key: HBASE-20
>                 URL: https://issues.apache.org/jira/browse/HBASE-20
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: Billy Pearson
>            Priority: Minor
>             Fix For: 0.2.0
> I thank we addressed this here
> HADOOP-2295
> but I have found it showing up again
> my hlog size is set to 250,000
> so on a recovery from a failed region server the recovery of scanning the logs takes
longer then the 
> hbase.hbasemaster.maxregionopen default of 30 secs
> and the master is thinks the region is open but the region server closes the region when
done recovering becuase the master sent a 
> MSG_REGION_CLOSE_WITHOUT_REPORT to the region server.
> I was able to get my table back online completely by adding 
> hbase.hbasemaster.maxregionopen  with a value of 300000 mili secs to my hbase-site.xml
> and restart.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message