Hello All,
I'd like to have a piece of advice regarding how my HDFS clients should handle
the NameNode high availability feature.
I have a complete setup running with ZKFC and I can see one active and one
standby NameNode. When I kill the active one, the standy gets active and when
the origina
I think you can simply use the nameservice (dfs.nameservices) which is
defined in hdfs-site.xml
The hdfs client should be able to resolve the current active namenode and
get the necessary information.
Thanks,
Sandeep Nemuri
ᐧ
On Wed, May 4, 2016 at 12:04 PM, Cecile, Adam wrote:
> Hello All,
>
>
___________
De : Sandeep Nemuri
Envoy? : mercredi 4 mai 2016 09:15
? : Cecile, Adam
Cc : user@hadoop.apache.org
Objet : Re: NameNode HA from a client perspective
I think you can simply use the nameservice (dfs.nameservices) which is defined
in hdfs-site.xm
) occurs, then repeat #2 and #3, starting from the next namenode url
in the list.
--Brahma Reddy Battula
From: Cecile, Adam [mailto:adam.cec...@hitec.lu]
Sent: 04 May 2016 16:26
To: Sandeep Nemuri
Cc: user@hadoop.apache.org
Subject: RE: NameNode HA from a client perspective
Hello,
I'm not
>
>
>
>
>
> --Brahma Reddy Battula
>
>
>
> *From:* Cecile, Adam [mailto:adam.cec...@hitec.lu]
> *Sent:* 04 May 2016 16:26
> *To:* Sandeep Nemuri
> *Cc:* user@hadoop.apache.org
> *Subject:* RE: NameNode HA from a client perspective
>
>
>
> Hello,
ecile, Adam; user@hadoop.apache.org
Objet : Re: NameNode HA from a client perspective
This could help you: https://pypi.python.org/pypi/PyHDFS/0.1.0
Thanks,
Sandeep
[https://mailfoogae.appspot.com/t?sender=abmhzYW5kZWVwNkBnbWFpbC5jb20%3D&type=zerocontent&guid=7e3cecdd-6d1b-4dbd-ba95-140c5f11e
