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 "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/02/21 19:08:18 UTC

[jira] [Commented] (YARN-4700) ATS storage has one extra record each time the RM got restarted

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

Naganarasimha G R commented on YARN-4700:
-----------------------------------------

hi [~gtCarrera9],  Thought  of taking this issue up, please reassign if you have already started working on this !
I think we can better consider default clusterID as static constant like "mycluster" / "yarncluster" ... thoughts?
cc /[~sjlee0]

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