Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <858103743.1224148124579.JavaMail.jira@brutus>
Date: Thu, 16 Oct 2008 02:08:44 -0700 (PDT)
From: "Rong-En Fan (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-932) Regionserver restart
In-Reply-To: <47195435.1224109364754.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-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640111#action_12640111 ] 

Rong-En Fan commented on HBASE-932:
-----------------------------------

I like the idea of having something to restart HRS automatically for a limit # of times. This is similar to what daemontools does [1]. 

[1] http://cr.yp.to/daemontools.html

> Regionserver restart
> --------------------
>
>                 Key: HBASE-932
>                 URL: https://issues.apache.org/jira/browse/HBASE-932
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>
> If we drop a flush or we fail close a write-ahead log, we currently shutdown the regionserver (we fail because of hdfs usually).  Rather than shut themselves down, how about they restart?  The restart at least in the HBASE-930 might fix the issue shaking DFSClient so it gets sense again.  Even is HDFS is bad, it'll come around eventually.  The HRS restarting itself plus HBASE-926 fix will make for fast recovery.

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