[
https://issues.apache.org/jira/browse/YARN-6616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745192#comment-16745192
]
Kuhu Shukla commented on YARN-6616:
-----------------------------------
Minor comment on
{code}
@Public
@Stable
public abstract long getSubmitTime();
@Private
@Unstable
public abstract void setSubmitTime(long submitTime);
{code}
Wondering how the getter is considered Stable and the setter is not. I see
other methods do the same but is that true for these particular ones or just an
artifact from older code?
I also wonder how this fix getting in would not break compatibility in a minor
release of 3.2. I am no expert at compatibility so pinging [~eepayne] and
[~haibochen] for helping with this.
Otherwise the patch looks good to me and I verified that the test failures are
unrelated. We need to check out the mapreduce build failure however.
> YARN AHS shows submitTime for jobs same as startTime
> ----------------------------------------------------
>
> Key: YARN-6616
> URL: https://issues.apache.org/jira/browse/YARN-6616
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.3
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Minor
> Attachments: 0001-YARN-6616.patch, 0002-YARN-6616.patch,
> 0003-YARN-6616.patch
>
>
> YARN AHS returns startTime value for both submitTime and startTime for the
> jobs. Looks the code sets the submitTime with startTime value.
> https://github.com/apache/hadoop/blob/branch-2.7.3/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common/src/main/java/org/apache/hadoop/yarn/server/webapp/dao/AppInfo.java#L80
> {code}
> curl --negotiate -u:
> http://prabhuzeppelin3.openstacklocal:8188/ws/v1/applicationhistory/apps
> <submittedTime>1495015537574</submittedTime><startedTime>1495015537574</startedTime><finishedTime>1495016384084</finishedTime>
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
