You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Billy Pearson (JIRA)" <ji...@apache.org> on 2008/01/18 22:50:34 UTC
[jira] Updated: (HADOOP-2660) Regions getting messages from master
to MSG_REGION_CLOSE_WITHOUT_REPORT
[ https://issues.apache.org/jira/browse/HADOOP-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Billy Pearson updated HADOOP-2660:
----------------------------------
Priority: Major (was: Critical)
> Regions getting messages from master to MSG_REGION_CLOSE_WITHOUT_REPORT
> -----------------------------------------------------------------------
>
> Key: HADOOP-2660
> URL: https://issues.apache.org/jira/browse/HADOOP-2660
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: Billy Pearson
> Fix For: 0.16.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 file
> and restart.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.