[
https://issues.apache.org/jira/browse/HADOOP-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561892#action_12561892
]
stack commented on HADOOP-2660:
-------------------------------
I concur that hbase startup is kinda ugly when there are loads of regions.
I've witnessed lots of thrashing with regions multiply assigned because startup
is taking too long out on the regionservers.
> 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 Core
> Issue Type: Bug
> Components: contrib/hbase
> Reporter: Billy Pearson
>
> 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.
