hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-5169) most of YARN events have timestamp of -1
Date Fri, 27 May 2016 03:55:13 GMT
Sangjin Lee created YARN-5169:

             Summary: most of YARN events have timestamp of -1
                 Key: YARN-5169
                 URL: https://issues.apache.org/jira/browse/YARN-5169
             Project: Hadoop YARN
          Issue Type: Bug
          Components: yarn
    Affects Versions: 2.7.2
            Reporter: Sangjin Lee

Most of the YARN events (subclasses of {{AbstractEvent}}) have timestamp of -1. {{AbstractEvent}}
have two constructors, one that initializes the timestamp to -1 and the other to the caller-provided
value. But most events use the former (thus timestamp of -1).

Some of the more common events, including {{ApplicationEvent}}, {{ContainerEvent}}, {{JobEvent}},
etc. do not set the timestamp.

The rationale for this behavior seems to be mentioned in {{AbstractEvent}}:
  // use this if you DON'T care about the timestamp
  public AbstractEvent(TYPE type) {
    this.type = type;
    // We're not generating a real timestamp here.  It's too expensive.
    timestamp = -1L;

This absence of the timestamp isn't really visible in many cases and therefore may have gone
unnoticed, but the timeline service exposes this problem very visibly.

This message was sent by Atlassian JIRA

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

View raw message