Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates
 209.85.220.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type;
        b=LbEBat3WYytOj6kjGxwck4f6uiba73TnkNrXccfEBLJDIsKrh7OLCx9LiE4yv3wkjK
         KDy2zu/1nI0hhX/of/mFESBoSJ6eOz57a5Ew+3rNqeDbXh5c0EK5dJt9GS7QAizH31h4
         9hNb7A15h6JvesL5i7rhGBGXKl2H2qH5jg/c0=
MIME-Version: 1.0
Sender: jdcryans@gmail.com
In-Reply-To: <31a243e70912071702o4cd13ebej87c205455a071ee9@mail.gmail.com>
References: <1260177255.30509.28.camel@pyro.bengueladev.com>
	 <31a243e70912071702o4cd13ebej87c205455a071ee9@mail.gmail.com>
Date: Mon, 7 Dec 2009 18:11:25 -0800
Message-ID: <31a243e70912071811l7caab100s8bc199ea28d6a55c@mail.gmail.com>
Subject: Re: Zookeeper hostname lookup
From: Jean-Daniel Cryans <jdcryans@apache.org>
To: hbase-user@hadoop.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I created a new jira about checking every bits of info we can to do
the comparison, please try my patch from
https://issues.apache.org/jira/browse/HBASE-2031

J-D

On Mon, Dec 7, 2009 at 5:02 PM, Jean-Daniel Cryans <jdcryans@apache.org> wrote:
> Richard,
>
> Actually what you're hitting isn't from the Zookeeper code but our
> HBase wrapper that starts the ZK quorum peers. What we're doing is
> that the peer needs an id when starting up and the way we make sure
> it's different on every started node is that we just use the index of
> the address in the hbase.zookeeper.quorum configuration. Maybe we
> could check not just the default hostname...
>
> J-D
>
> On Mon, Dec 7, 2009 at 1:14 AM, Richard Dorman <richard@bengueladev.com> wrote:
>> I'm trying to startup a quorum of Zookeeper servers in a cluster,
>> however, Zookeeper is failing to start because it cannot find its
>> hostname in the list of Zookeeper quorum servers.
>>
>> I know this problem is well documented on the WIKI, however, my
>> situation is a little different. The allocation of a node to become a
>> Zookeeper is done dynamically by a management service running else where
>> on the cluster. This node then associates its IP with a hostname in the
>> Zookeeper quorum list. The hostname is not the default hostname of the
>> node. The node may associate its IP with multiple hostnames for each
>> service that it is allocated.
>>
>> This causes a problem when Zookeeper starts. Zookeeper does a
>> getdefaulthost which will return the nodes default hostname and not the
>> associated hostname.
>>
>> So my questions are:
>>
>> 1. Is it possible to resolve this some other way? We are not running DNS
>> (hostname associations are managed by our own services). We also cannot
>> use the nodes ip address as the nodes are allocated dynamically.
>> Dynamically updating the config files is also not practical.
>>
>> 2. Why does Zookeeper need to test whether its hostname is in the
>> Zookeeper quorim list? Can this safely be disabled?
>>
>> Richard
>>
>>
>>
>