You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jonathan Hung (JIRA)" <ji...@apache.org> on 2019/01/23 02:55:00 UTC
[jira] [Created] (YARN-9222) Change startTime semantics for RMApp
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-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org