hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hung (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-9222) Change startTime semantics for RMApp
Date Wed, 23 Jan 2019 02:55:00 GMT
Jonathan Hung created YARN-9222:
-----------------------------------

             Summary: Change startTime semantics for RMApp
                 Key: YARN-9222
                 URL: https://issues.apache.org/jira/browse/YARN-9222
             Project: Hadoop YARN
          Issue Type: Bug
            Reporter: Jonathan Hung


Currently submitTime for rmApp is based on when app is submitted to RMAppManager:
{noformat}
rmAppManager.submitApplication(submissionContext,
    System.currentTimeMillis(), user);{noformat}
Then RMAppManager#createAndPopulateNewRMApp does some validation (queue routing, app priority,
etc), then the RMAppImpl object is created, at which point the startTime is populated:
{noformat}
if (startTime <= 0) {
  this.startTime = this.systemClock.getTime();
} else {
  this.startTime = startTime;
}{noformat}
In general it seems there shouldn't be much difference between submitTime and startTime. It
makes more sense to change startTime to when the app actually started. One possible solution
is to (re)populate startTime when application master registers with RM.

One issue may be compatibility, especially if there are large scheduling delays.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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


Mime
View raw message