Return-Path: 
 <user-return-15886-apmail-hadoop-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id C24E311C9B
	for <apmail-hadoop-user-archive@minotaur.apache.org>;
 Sat, 28 Jun 2014 02:28:35 +0000 (UTC)
Received: (qmail 68742 invoked by uid 500); 28 Jun 2014 02:28:31 -0000
Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org
Received: (qmail 68634 invoked by uid 500); 28 Jun 2014 02:28:31 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Delivered-To: moderator for user@hadoop.apache.org
Received: (qmail 80708 invoked by uid 99); 27 Jun 2014 07:02:25 -0000
X-ASF-Spam-Status: No, hits=2.9 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_HELO_PASS,SPF_NEUTRAL,WEIRD_PORT
X-Spam-Check-By: apache.org
Received-SPF: neutral (athena.apache.org: local policy)
X-Sender-Id: sozotechnologies|x-authuser|jcfernandez@redoop.org
X-Sender-Id: sozotechnologies|x-authuser|jcfernandez@redoop.org
X-MC-Relay: Neutral
X-MailChannels-SenderId: sozotechnologies|x-authuser|jcfernandez@redoop.org
X-MailChannels-Auth-Id: sozotechnologies
MIME-Version: 1.0
X-Received: by 10.60.131.232 with SMTP id op8mr21201670oeb.42.1403852515615;
 Fri, 27 Jun 2014 00:01:55 -0700 (PDT)
In-Reply-To: 
 <CAMhYJnwu6EUTpFO9VD5YbYN0PzvveReh8LRhMNznoTj7Nz4YKg@mail.gmail.com>
References: 
 <CAMhYJnwu6EUTpFO9VD5YbYN0PzvveReh8LRhMNznoTj7Nz4YKg@mail.gmail.com>
Date: Fri, 27 Jun 2014 09:01:55 +0200
Message-ID: 
 <CACaUSBUpC_YDCwr_Us4nXiuXatXTCh1QtjApGGMRFb_VgCN=Gg@mail.gmail.com>
Subject: Re: Configuring Hadoop Client: Where is fail-over configured.
From: Juan Carlos <jcfernandez@redoop.org>
To: "user@hadoop.apache.org" <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=047d7b47266a82aad504fccbe21c
X-AuthUser: jcfernandez@redoop.org
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7b47266a82aad504fccbe21c
Content-Type: text/plain; charset=UTF-8

Hi Charley,

in hdfs-site.xml you can find the property dfs.ha.namenodes, setting this
property every client will know which NN are elegibles to be active,
nothing else are required in client.

Regards.


2014-06-26 21:30 GMT+02:00 Charley Newtonne <cnewtonne@gmail.com>:

> I have hadoop 2.4 installed in HA mode using QJM. I have verified the
> cluster failover works as expected. The java clients are configured to
> connect to the active NN by specifying the hdf://nn1.company.com:8020. If
> this nn1 is down, how's the client know the location of the standby nn.
> Where is the client spillover configured?
>
> I have seen some references that this is configured in client's
> core-site.xml, but this file only specifies the defaultFS (which has the
> value of the logical cluster name) and ZK quorum nodes. None of these
> appear to be related to client side failover.
>
> Thanks in advance
>

--047d7b47266a82aad504fccbe21c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi Charley,<br><br></div>in hdfs-site.xml y=
ou can find the property dfs.ha.namenodes, setting this property every clie=
nt will know which NN are elegibles to be active, nothing else are required=
 in client.<br>
<br></div>Regards.<br></div></div><div class=3D"gmail_extra"><br><br><div c=
lass=3D"gmail_quote">2014-06-26 21:30 GMT+02:00 Charley Newtonne <span dir=
=3D"ltr">&lt;<a href=3D"mailto:cnewtonne@gmail.com" target=3D"_blank">cnewt=
onne@gmail.com</a>&gt;</span>:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I have hadoop 2.4 inst=
alled in HA mode using QJM. I have verified the cluster failover works as e=
xpected. The java clients are configured to connect to the active NN by spe=
cifying the hdf://<a href=3D"http://nn1.company.com:8020" target=3D"_blank"=
>nn1.company.com:8020</a>. If this nn1 is down, how&#39;s the client know t=
he location of the standby nn. Where is the client spillover configured?</d=
iv>

<div><br></div><div>I have seen some references that this is configured in =
client&#39;s core-site.xml, but this file only specifies the defaultFS (whi=
ch has the value of the logical cluster name) and ZK quorum nodes. None of =
these appear to be related to client side failover.</div>

<div><br></div><div>Thanks in advance</div></div>
</blockquote></div><br></div>

--047d7b47266a82aad504fccbe21c--