Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1496773302.1209010761414.JavaMail.jira@brutus>
Date: Wed, 23 Apr 2008 21:19:21 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-20) Regions getting messages from master to
 MSG_REGION_CLOSE_WITHOUT_REPORT
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-20.
------------------------

    Resolution: Fixed

OK.  Thanks for chirping up Billy.  I"ll close it as fixed (because of reasons given above).

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