You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Billy Pearson (JIRA)" <ji...@apache.org> on 2008/04/24 03:53:21 UTC

[jira] Commented: (HBASE-20) Regions getting messages from master to MSG_REGION_CLOSE_WITHOUT_REPORT

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

Billy Pearson commented on HBASE-20:
------------------------------------

I do not have a spare cluster of servers any more I had to put my them to work so if you fill this has been addressed then fill free to 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 file
> and restart.

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