Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <685664910.1213211085175.JavaMail.jira@brutus>
Date: Wed, 11 Jun 2008 12:04:45 -0700 (PDT)
From: "Jean-Daniel Cryans (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Updated: (HBASE-546) Use Zookeeper in HBase
In-Reply-To: <1900020967.1206556165060.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-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Daniel Cryans updated HBASE-546:
-------------------------------------

    Attachment: zookeeper-config.patch

This is the kind of patch i was talking on IRC. Works on 2.2.1

With this, we would have to distribute Zookeeper with HBase. The processes would be started using start-hbase.sh as any other process. In HBase, we read the ZK server config (which would be in hbase-site.xml) and there you go, you know where to connect.

> Use Zookeeper in HBase
> ----------------------
>
>                 Key: HBASE-546
>                 URL: https://issues.apache.org/jira/browse/HBASE-546
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Bryan Duxbury
>            Priority: Trivial
>         Attachments: zookeeper-config.patch
>
>
> Zookeeper =~ Chubby. This means that we could take advantage of a distributed lock manager to coordinate things like failover masters, regionservers staying online when master is dead, atomic region->regionserver assignments, etc. There are a lot of opportunities for improvements here. Please add discussions of particular features in comments or sub-tasks.

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