[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Naganarasimha G R updated YARN-4700: ------------------------------------ Attachment: YARN-4700-YARN-2928.v1.001.patch Hi [~vrushalic], [~sjlee0] & [~varun_saxena], Please find the attached patch which tries to consider for the app created and as well as app finished event updating the *FlowActivityTable* Only concern is, may be i did not get the complete essence of {{TestHBaseStorageFlowActivity.testWriteFlowRunMinMax}} testcase hence its failing, IIUC there should be 4 entries in FlowActivity table as these are 4 diff apps of the same flow right ? correct me if i am wrong. > 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 > Attachments: YARN-4700-YARN-2928.v1.001.patch, > YARN-4700-YARN-2928.wip.patch > > > 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)