Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-dev@hadoop.apache.org
MIME-Version: 1.0
In-Reply-To: <0FE709BE-FC67-43B4-964D-F6F8AF7D4248@hortonworks.com>
References: <4335BFA2-D106-4AC5-8C21-9D8AB2F39516@hortonworks.com>
	<CADbBEnugXOT5APgL2sybcmT2kuW-VnRXO4cHA-ffhkMiZrs_Ng@mail.gmail.com>
	<0FE709BE-FC67-43B4-964D-F6F8AF7D4248@hortonworks.com>
Date: Tue, 15 Dec 2015 10:48:09 +0530
Message-ID: 
 <CANOghCXm8TOR3esAm69ifNWUKE9PYj2WBcRrexSQDEWx_VuJkQ@mail.gmail.com>
Subject: Re: [Timeline V2 branch] Latest timeline v2 and SMP problem
From: Varun Saxena <vsaxena.varun@gmail.com>
To: Li Lu <llu@hortonworks.com>
Cc: "yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
 Sangjin Lee <sjlee@twitter.com>,
	Junping Du <jdu@hortonworks.com>,
 Vrushali Channapattan <vrushali@twitter.com>,
	Joep Rottinghuis <joep@twitter.com>,
	"Naganarasimha G R (Naga)" <garlanaganarasimha@huawei.com>
Content-Type: multipart/alternative; boundary=001a113edd705a33d40526e8ea93

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

Hi Li,

This is because we are registering the event in serviceStart() instead of
serviceInit().
As SMP is the last service in the list, its started right in the end i.e.
even after all the RPCs', UI related stuff.

This can cause an app flow to start before the SMP/V2Publisher service has
even started. This is what causes the issue.

You want to raise JIRA for this issue or should I ? I can handle it.

Regards,
Varun Saxena.

On Tue, Dec 15, 2015 at 8:35 AM, Li Lu <llu@hortonworks.com> wrote:

> Thanks Sangjin. I=E2=80=99ll keep tracing this. Meanwhile, if anybody has
> reproduced the problem, please feel free to let me know. Thanks!
>
> Li Lu
>
> On Dec 14, 2015, at 18:16, Sangjin Lee <sjlee0@gmail.com> wrote:
>
> Can you bisect the commits to see if you can isolate which commit
> introduced the issue?
>
> On Mon, Dec 14, 2015 at 5:39 PM, Li Lu <llu@hortonworks.com> wrote:
>
> Hi YARN developers working on Timeline v2 (YARN-2928) branch,
>
> I just realized I=E2=80=99ve accidentally turned off SMP for my local Tim=
eline v2
> build. After I turned yarn.system-metrics-publisher.enabled back on, the =
RM
> fails to start with the following FATAL message:
>
> 2015-12-14 17:27:54,125 INFO  ipc.Server (Server.java:run(797)) - IPC
> Server listener on 8033: starting
> 2015-12-14 17:27:54,127 FATAL event.AsyncDispatcher
> (AsyncDispatcher.java:dispatch(189)) - Error in dispatcher thread true
> java.lang.Exception: No handler for registered for class
>
> org.apache.hadoop.yarn.server.resourcemanager.metrics.AbstractSystemMetri=
csPubli
> sher$SystemMetricsEventType
>        at
>
> org.apache.hadoop.yarn.event.AsyncDispatcher.dispatch(AsyncDispatcher.jav=
a:185)
>        at
>
> org.apache.hadoop.yarn.event.AsyncDispatcher$1.run(AsyncDispatcher.java:1=
09)
>        at java.lang.Thread.run(Thread.java:745)
> 2015-12-14 17:27:54,127 INFO  event.AsyncDispatcher
> (AsyncDispatcher.java:register(208)) - Registering class
> org.apache.hadoop.yarn.serve
>
> r.resourcemanager.metrics.AbstractSystemMetricsPublisher$SystemMetricsEve=
ntType
> for class org.apache.hadoop.yarn.server.resourcemanager.m
> etrics.TimelineServiceV2Publisher$TimelineV2EventHandler
>
> Interestingly, we=E2=80=99re registering this class to timeline v2 handle=
r in the
> next line of log. I=E2=80=99m wondering if this is caused by some of my m=
issing
> configs, or a newly introduced issue? Has anybody on feature-YARN-2928
> branch noticed this issue? Thanks!
>
> Li Lu
>
>
>
>

--001a113edd705a33d40526e8ea93--