[ https://issues.apache.org/jira/browse/YARN-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172357#comment-15172357 ]
Naganarasimha G R commented on YARN-4700: ----------------------------------------- Hi [~sjlee0], Based on the points from [~vrushalic] and [~varun_saxena], was creating a patch such that {{HBaseTimelineWriterImpl.storeInFlowActivityTable}} uses {{FlowActivityRowKey.getRowKey(clusterId, te.getCreatedTime(), userId, flowName)}} instead of the other overloaded method which doesn't take the timestamp. This would take care of of calling {{TimelineStorageUtils.getTopOfTheDayTimestamp()}} right ? > 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)