Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of nkeywal@gmail.com designates
 209.85.217.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACp05np-RLjRjBb0ofefAybEKCkuJ2Vc6JLr9fsmKbRtX_KQKg@mail.gmail.com>
References: <1353875832706-4034362.post@n3.nabble.com>
 <CAMVC6RPPUnhZ9cxb7FUqB9PULXipJX7QA8xjTvMMJMSr_Rp=jg@mail.gmail.com>
 <CAMVC6RN1HUvcP01WPw8YJhvZ01XXYYtJKp7HOUjJe5mdT2R8dw@mail.gmail.com>
 <CAMVC6RP=ar+DO3fs+CFeNHg43bLw_u3OyS_VHrX6CHPcZ9WWyw@mail.gmail.com>
 <CACp05np-RLjRjBb0ofefAybEKCkuJ2Vc6JLr9fsmKbRtX_KQKg@mail.gmail.com>
From: Nicolas Liochon <nkeywal@gmail.com>
Date: Mon, 26 Nov 2012 16:28:25 +0100
Message-ID: 
 <CAPcDmSscJ5KoqOkkNGfSHE7xqRAtdV4A9w7nAbfbW6QD_cz4QQ@mail.gmail.com>
Subject: Re: Connecting to standalone HBase from a remote client
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d04071613ce086004cf67960a

--f46d04071613ce086004cf67960a
Content-Type: text/plain; charset=ISO-8859-1

Yes, it's not useful to set the master address in the client. I suppose it
was different a long time ago, hence there are some traces on different
documentation.
The master references itself in ZooKeeper. So if the master finds itself to
be "locahost", ZooKeeper will contain "locahost", and the clients on
another computer won't be able to connect. The issue lies on the master
host, not the client.

On Mon, Nov 26, 2012 at 4:06 PM, matan <matan@cloudaloe.org> wrote:

>  also don't really understand why it has to be set in the client, as
> according to the flow you describe, the client is getting all it needs to
> know from zookeeper (?).
>

--f46d04071613ce086004cf67960a--