[ 
https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15169531#comment-15169531
 ] 

Li Lu commented on YARN-4700:
-----------------------------

I think the redundant events are coming from the work preserving RM restart, 
where the RM tries to "replay" application lifecycle events in the state store. 
I don't remember the JIRA number for fixing this for SMP (but I do remember 
[~Naganarasimha] was involved in the discussion), but seems like the conclusion 
was to handle this on the SMP/storage side rather than the RM side. For us, 
most of the tables are fine, but the flow activity table we need to distinguish 
a "real" activity from a replayed activity. 

> 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)

Reply via email to