Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 26 Feb 2016 23:33:18 +0000 (UTC)
From: "Li Lu (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12939901.1455737263000.161589.1456529598243@Atlassian.JIRA>
In-Reply-To: <JIRA.12939901.1455737263000@Atlassian.JIRA>
References: <JIRA.12939901.1455737263000@Atlassian.JIRA>
 <JIRA.12939901.1455737263737@arcas>
Subject: [jira] [Commented] (YARN-4700) ATS storage has one extra record
 each time the RM got restarted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

bq. In the code that writes to the flow activity table, can we check the application status and make a decision not to write them?
I'm not very familiar with the replayed event sequence, but will we receive an application finished event for each of the finished applications? If so, it will make distinguishing the real events from the replayed events very difficult? [~Naganarasimha] what's your experience working with the SMP? Thanks! 

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