Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <30201797.49221277420150690.JavaMail.jira@thor>
Date: Thu, 24 Jun 2010 18:55:50 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Commented: (HBASE-2700) Handle master failover for regions
 in transition
In-Reply-To: <27617847.33701276033580816.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack commented on HBASE-2700:
------------------------------

We seem to be making progress on this thread.  Looks like we've saved having to have a server list up in zk.

.bq I'm interested in a scenario where region state up in zk is not sufficient or not representative.

I don't have specifics.  Past experience would have it that there'll likely be holes or transition modes we didn't consider.

.bq I see you have no confidence in ZK....

You have me wrong here.  Doing transitions via ZK has my total endorsement.  I look forward to the fat patches that move us there.

> Handle master failover for regions in transition
> ------------------------------------------------
>
>                 Key: HBASE-2700
>                 URL: https://issues.apache.org/jira/browse/HBASE-2700
>             Project: HBase
>          Issue Type: Sub-task
>          Components: master, zookeeper
>            Reporter: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.21.0
>
>
> To this point in HBASE-2692 tasks we have moved everything for regions in transition into ZK, but we have not fully handled the master failover case.  This is to deal with that and to write tests for it.

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