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 <adam.cec...@hitec.lu> wrote: > 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 original one get back online it turns into a standby node, perfect. > > However I'm not sure how my client apps should handle this, a couple of > ideas: > * Handle the bad HTTP code from standby node to switch to the other one > * Integrate Zookeeper client to query for the current active node > * Hack something like a shared-ip linked to the active node > > Then I'll have to handle a switch that may occurs during the execution of > a client app: should I just crash and rely on the cluster to restart the > job. > > > Thanks in advance, > > Best regards from Luxembourg. > -- * Regards* * Sandeep Nemuri*
