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


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

stack resolved HBASE-412.
-------------------------

    Resolution: Fixed

Should be fixed by HBASE-505 and by our doubling of default for region open timeout.

> unable to report to master
> --------------------------
>
>                 Key: HBASE-412
>                 URL: https://issues.apache.org/jira/browse/HBASE-412
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>            Reporter: Billy Pearson
>            Priority: Minor
>             Fix For: 0.2.0
>
>
> I have been getting these messages on my region server when they are under load
> {code}
> FATAL org.apache.hadoop.hbase.HRegionServer: unable to report to master for 30927 milliseconds - aborting server
> {code}
> Seams something is blocking the lease check in or something like that
> I know this is not a network issue as this has happened on a region server on the same node as the master.
> also I have updated hbase.regionserver.handler.count to 100 to make sure that was not the issue and the doc say that that is used for the master so its not lack of open handles to the master.
> kind of a pain becuase it crashes the region server causing the hlogs to be used to restore
> This is the messages right after the above and then the server shuts down if we can not find whats goiong on can we at lease make the server shutdown safely flushing memcache and closeing all logs so we do not have to do a restore on the next server that gets assigned the regions.
> {code}
> INFO org.apache.hadoop.ipc.Server: Stopping server on 60020
> {code}

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