[
https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168063#comment-15168063
]
Sangjin Lee commented on YARN-4700:
-----------------------------------
[~gtCarrera9], can you provide the exact row keys in this problem scenario?
From what I can see in the code, if you're not setting the cluster id in the
configuration (under key "yarn.resourcemanager.cluster-id"), it should be the
default value ("yarn_cluster"). I'm not sure where the duplicate keys are
coming from. Once we see the duplicate row keys for the same app, it should
become clearer.
Are you seeing this with a DS app or a MR app?
> 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
>
> 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)
