[
https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169734#comment-15169734
]
Varun Saxena commented on YARN-4700:
------------------------------------
When we recover an app we can also get start and finish time for an app from
the state store. This is updated then in RMAppImpl.
So when the event is replayed and reported to ATSv2, app start event would
carry the same time as the time at which app originally started.
Currently for flow activity table, the inverted top of the day timestamp is
generated based on current system time. I think we can instead use the
timestamp coming in the event.
That should resolve this issue.
cc [~sjlee0], [~vrushalic]. I do not see any issue in using event's timestamp.
Do you see any ?
> ATS storage has one extra record each time the RM got restarted
> ---------------------------------------------------------------
>
> Key: YARN-4700
> URL: https://issues.apache.org/jira/browse/YARN-4700
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Li Lu
> Assignee: Naganarasimha G R
> Labels: yarn-2928-1st-milestone
>
> When testing the new web UI for ATS v2, I noticed that we're creating one
> extra record for each finished application (but still hold in the RM state
> store) each time the RM got restarted. It's quite possible that we add the
> cluster start timestamp into the default cluster id, thus each time we're
> creating a new record for one application (cluster id is a part of the row
> key). We need to fix this behavior, probably by having a better default
> cluster id.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
