Mailing-List: contact user-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hive.apache.org
Received-SPF: pass (athena.apache.org: domain of nitinpawar432@gmail.com
 designates 209.85.160.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGd0WxLuFiR+dMkui7bPYEvkUwAu2CW0soX6EB-+Xtj=uDaX8g@mail.gmail.com>
References: 
 <CAGd0WxLuFiR+dMkui7bPYEvkUwAu2CW0soX6EB-+Xtj=uDaX8g@mail.gmail.com>
Date: Wed, 5 Nov 2014 12:31:38 +0530
Message-ID: 
 <CAORpBshT+N98iHaekBNpL3t_761Sn+wQaG-934pdfxPXT7Ko=Q@mail.gmail.com>
Subject: Re: Unix script for identifying current active namenode in a HA
 cluster
From: Nitin Pawar <nitinpawar432@gmail.com>
To: "user@hive.apache.org" <user@hive.apache.org>
Content-Type: multipart/alternative; boundary=089e013a2636b5649805071726ee

--089e013a2636b5649805071726ee
Content-Type: text/plain; charset=UTF-8

+1
If you can optionally add hadoop home directory in the script and use that
in path, it can be used out of the box.

Also can you share this on github

On Wed, Nov 5, 2014 at 10:02 AM, Devopam Mittra <devopam@gmail.com> wrote:

> hi All,
> Please find attached a simple shell script to dynamically determine the
> active namenode in the HA Cluster and subsequently run the Hive job / query
> via Talend OS generated workflows.
>
> It was tried successfully on a HDP2.1 cluster with 2 nn, 7 dn running on
> CentOS 6.5.
> Each ETL job invokes this script first in our framework to derive the NN
> FQDN and then run the hive jobs subsequently to avoid failures.
> Takes a max. of 2 secs to execute (small cost in our case, as compared to
> dealing with a failure and then recalculating the NN to resubmit the job).
>
> Sharing it with you in case you can leverage the same without spending
> effort to code it.
>
> Do share your feedback/ fixes if you spot any.
>
> --
> Devopam Mittra
> Life and Relations are not binary
>


-- 
Nitin Pawar

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

<div dir=3D"ltr">+1=C2=A0<div>If you can optionally add hadoop home directo=
ry in the script and use that in path, it can be used out of the box.=C2=A0=
</div><div><br></div><div>Also can you share this on github=C2=A0</div></di=
v><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Nov 5, =
2014 at 10:02 AM, Devopam Mittra <span dir=3D"ltr">&lt;<a href=3D"mailto:de=
vopam@gmail.com" target=3D"_blank">devopam@gmail.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">hi All,<div>Please find =
attached a simple shell script to dynamically determine the active namenode=
 in the HA Cluster and subsequently run the Hive job / query via Talend OS =
generated workflows.<br clear=3D"all"><div><br></div><div>It was tried succ=
essfully on a HDP2.1 cluster with 2 nn, 7 dn running on CentOS 6.5.</div><d=
iv>Each ETL job invokes this script first in our framework to derive the NN=
 FQDN and then run the hive jobs subsequently to avoid failures.=C2=A0</div=
><div>Takes a max. of 2 secs to execute (small cost in our case, as compare=
d to dealing with a failure and then recalculating the NN to resubmit the j=
ob).</div><div><br></div><div>Sharing it with you in case you can leverage =
the same without spending effort to code it.</div><div><br></div><div>Do sh=
are your feedback/ fixes if you spot any.</div><span class=3D"HOEnZb"><font=
 color=3D"#888888"><div><br></div>-- <br><div>Devopam Mittra<br>Life and Re=
lations are not binary</div>
</font></span></div></div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature">Nitin Pawar<br></div>
</div>

--089e013a2636b5649805071726ee--