Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 22 Mar 2011 21:08:07 +0000 (UTC)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <183511613.4702.1300828087975.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1771506091.4442.1300821605667.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-3687) Bulk assign on startup should
 handle a ServerNotRunningException
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray commented on HBASE-3687:
--------------------------------------

Shouldn't the RS not check in to the master with an RPC until it is available?

> Bulk assign on startup should handle a ServerNotRunningException
> ----------------------------------------------------------------
>
>                 Key: HBASE-3687
>                 URL: https://issues.apache.org/jira/browse/HBASE-3687
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.90.2
>
>         Attachments: 3687.txt
>
>
> On startup, we do bulk assign.  At the moment, if any problem during bulk assign, we consider startup failed and expectation is that you need to retry (We need to make this better but that is not what this issue is about).  One exception that we should handle is the case where a RS is slow coming up and its rpc is not yet up listening.  In this case it will throw: ServerNotRunningException.  We should retry at least this one exception during bulk assign.
> We had this happen to us starting up a prod cluster.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira