Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Received-SPF: pass (nike.apache.org: domain of david.mccauley@wandisco.com
 designates 209.85.216.41 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGjSOKUfD1Zrrz2FX0tEZwMg-Weiqm24QdaPOo2_v1CXNXSLnA@mail.gmail.com>
References: 
 <CAEgC1-kFidLegf8-4b2eJCVB=PVGYWAVU0HKJxHb8LVLob-NJg@mail.gmail.com>
	<CAGjSOKUfD1Zrrz2FX0tEZwMg-Weiqm24QdaPOo2_v1CXNXSLnA@mail.gmail.com>
Date: Thu, 10 Jul 2014 18:18:05 +0100
Message-ID: 
 <CAEgC1-n7-7Ykg4zEVT=X-5Xp+4uYr0cbtX5F7KnMCrDsue0QBQ@mail.gmail.com>
Subject: Re: Quick Links Disabled
From: David McCauley <david.mccauley@wandisco.com>
To: dev@ambari.apache.org
Content-Type: multipart/mixed; boundary=001a11c1358a02238704fdda0261

--001a11c1358a02238704fdda0261
Content-Type: multipart/alternative; boundary=001a11c1358a02238104fdda025f

--001a11c1358a02238104fdda025f
Content-Type: text/plain; charset=UTF-8

Hi Yusaku,
I am using 1.5.1 at the moment, I have also used 1.6.0 and as you say the
links are not greyed out but only link to blank pages.

I think the problem lies in the fact that we have active-active NameNodes
with replication between them, Ambari is probably getting confused as a
result. From the screenshot as you can see we only display one of the
active NameNodes, the other two are alive and well but Ambari is unaware of
them.

If I could make Ambari just link to the primary NameNode that would
probably suffice for now. I'm going to look into the proper solution as we
progress.

Thanks very much!
Dave


On 10 July 2014 16:10, Yusaku Sako <yusaku@hortonworks.com> wrote:

> Hi David,
>
> What version of Ambari are you using?
> My guess is that due to your setup, Ambari thinks both NameNodes are
> in Standby (or not able to retrieve the active/standby status) and not
> enabling the Quick Links.
> Can you take a screenshot of what you are seeing?
> In 1.6.0 and higher, you should always be able to access Quick Links
> for NameNodes regardless of their active/standby state:
> https://issues.apache.org/jira/browse/AMBARI-5652
>
> Yusaku
>
> On Thu, Jul 10, 2014 at 6:16 AM, David McCauley
> <david.mccauley@wandisco.com> wrote:
> > Hi,
> > I am having an issue with the 'Quick Links' menu 'greying out' within the
> > Services->HDFS page containing NameNode UI, logs etc. To reach this state
> > we have integrated it with our Non-Stop NameNode product which requires
> > HDFS with quite specific HA settings. These have quite possibly have
> > interfered with the standard HA setup, and may be a possible issue.
> >
> > Unfortunately I am not a web developer by any means but I have tried to
> run
> > Ember Inspector on the page but it claims that an Ember application is
> not
> > detected. I am using version 1.3.1 and the latest Chrome if this helps.
> >
> > If I could just get some suggestions on the problem or advice on how to
> > debug the issue that would be excellent, as no doubt there will be more
> > issues to diagnose. :)
> >
> > Thanks in advance for any help,
> > Dave
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>

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

<div dir=3D"ltr">Hi=C2=A0<span style=3D"font-family:arial,sans-serif;font-s=
ize:13px">Yusaku,</span><div><span style=3D"font-family:arial,sans-serif;fo=
nt-size:13px">I am using 1.5.1 at the moment, I have also used 1.6.0 and as=
 you say the links are not greyed out but only link to blank pages.</span><=
/div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">I t=
hink the problem lies in the fact that we have active-active NameNodes with=
 replication between them, Ambari is probably getting confused as a result.=
 From the screenshot as you can see we only display one of the active NameN=
odes, the other two are alive and well but Ambari is unaware of them.</span=
></div>
<div><br></div><div>If I could make Ambari just link to the primary NameNod=
e that would probably suffice for now. I&#39;m going to look into the prope=
r solution as we progress.</div><div><br></div><div>Thanks very much!</div>
<div>Dave</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 10 July 2014 16:10, Yusaku Sako <span dir=3D"ltr">&lt;<a href=3D=
"mailto:yusaku@hortonworks.com" target=3D"_blank">yusaku@hortonworks.com</a=
>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi David,<br>
<br>
What version of Ambari are you using?<br>
My guess is that due to your setup, Ambari thinks both NameNodes are<br>
in Standby (or not able to retrieve the active/standby status) and not<br>
enabling the Quick Links.<br>
Can you take a screenshot of what you are seeing?<br>
In 1.6.0 and higher, you should always be able to access Quick Links<br>
for NameNodes regardless of their active/standby state:<br>
<a href=3D"https://issues.apache.org/jira/browse/AMBARI-5652" target=3D"_bl=
ank">https://issues.apache.org/jira/browse/AMBARI-5652</a><br>
<br>
Yusaku<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Thu, Jul 10, 2014 at 6:16 AM, David McCauley<br>
&lt;<a href=3D"mailto:david.mccauley@wandisco.com">david.mccauley@wandisco.=
com</a>&gt; wrote:<br>
&gt; Hi,<br>
&gt; I am having an issue with the &#39;Quick Links&#39; menu &#39;greying =
out&#39; within the<br>
&gt; Services-&gt;HDFS page containing NameNode UI, logs etc. To reach this=
 state<br>
&gt; we have integrated it with our Non-Stop NameNode product which require=
s<br>
&gt; HDFS with quite specific HA settings. These have quite possibly have<b=
r>
&gt; interfered with the standard HA setup, and may be a possible issue.<br=
>
&gt;<br>
&gt; Unfortunately I am not a web developer by any means but I have tried t=
o run<br>
&gt; Ember Inspector on the page but it claims that an Ember application is=
 not<br>
&gt; detected. I am using version 1.3.1 and the latest Chrome if this helps=
.<br>
&gt;<br>
&gt; If I could just get some suggestions on the problem or advice on how t=
o<br>
&gt; debug the issue that would be excellent, as no doubt there will be mor=
e<br>
&gt; issues to diagnose. :)<br>
&gt;<br>
&gt; Thanks in advance for any help,<br>
&gt; Dave<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
CONFIDENTIALITY NOTICE<br>
NOTICE: This message is intended for the use of the individual or entity to=
<br>
which it is addressed and may contain information that is confidential,<br>
privileged and exempt from disclosure under applicable law. If the reader<b=
r>
of this message is not the intended recipient, you are hereby notified that=
<br>
any printing, copying, dissemination, distribution, disclosure or<br>
forwarding of this communication is strictly prohibited. If you have<br>
received this communication in error, please contact the sender immediately=
<br>
and delete it from your system. Thank You.<br>
</font></span></blockquote></div><br></div>

--001a11c1358a02238104fdda025f--

--001a11c1358a02238704fdda0261--