Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 23 May 2016 17:44:14 +0000 (UTC)
From: "Li Lu (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12970185.1463439238000.267912.1464025454655@Atlassian.JIRA>
In-Reply-To: <JIRA.12970185.1463439238000@Atlassian.JIRA>
References: <JIRA.12970185.1463439238000@Atlassian.JIRA> <JIRA.12970185.1463439238188@arcas>
Subject: [jira] [Commented] (YARN-5094) some YARN container events have
 timestamp of -1 in REST output
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 23 May 2016 17:44:16 -0000


    [ https://issues.apache.org/jira/browse/YARN-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296707#comment-15296707 ] 

Li Lu commented on YARN-5094:
-----------------------------

bq. We can either populate the timestamp in ContainerEvent/ApplicationEvent/LocalizationEvent or take current system time and populate the timestamp in publish***Event methods(or other publish methods) in NMTimelinePublisher as these are direct calls from ContainerManagerImpl/ContainersMonitorImpl.

Yes. I'm relatively conservative on the first approach, since there are notes in AbstractEvent saying that:
{code}
// We're not generating a real timestamp here.  It's too expensive.
{code}

Having seen this and also the SMP design in RM I think passing in timestamp would be a better approach? 

> some YARN container events have timestamp of -1 in REST output
> --------------------------------------------------------------
>
>                 Key: YARN-5094
>                 URL: https://issues.apache.org/jira/browse/YARN-5094
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>    Affects Versions: YARN-2928
>            Reporter: Sangjin Lee
>            Assignee: Li Lu
>              Labels: yarn-2928-1st-milestone
>
> Some events in the YARN container entities have timestamp of -1. The RM-generated container events have proper timestamps. It appears that it's the NM-generated events that have -1: YARN_CONTAINER_CREATED, YARN_CONTAINER_FINISHED, YARN_NM_CONTAINER_LOCALIZATION_FINISHED, YARN_NM_CONTAINER_LOCALIZATION_STARTED.
> In the YARN container page,
> {noformat}
> {
> id: "YARN_CONTAINER_CREATED",
> timestamp: -1,
> info: { }
> },
> {
> id: "YARN_CONTAINER_FINISHED",
> timestamp: -1,
> info: {
> YARN_CONTAINER_EXIT_STATUS: 0,
> YARN_CONTAINER_STATE: "RUNNING",
> YARN_CONTAINER_DIAGNOSTICS_INFO: ""
> }
> },
> {
> id: "YARN_NM_CONTAINER_LOCALIZATION_FINISHED",
> timestamp: -1,
> info: { }
> },
> {
> id: "YARN_NM_CONTAINER_LOCALIZATION_STARTED",
> timestamp: -1,
> info: { }
> }
> {noformat}
> I think the data itself is OK, but the values are not being populated in the REST output?


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org