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

Sangjin Lee commented on YARN-4700:
-----------------------------------

These are the current default values that are being set as the context info 
(which is then used as part of the row key):
{code:title=AppLevelTimelineCollector.java}
    context.setClusterId(conf.get(YarnConfiguration.RM_CLUSTER_ID,
        YarnConfiguration.DEFAULT_RM_CLUSTER_ID));
    // Set the default values, which will be updated with an RPC call to get the
    // context info from NM.
    // Current user usually is not the app user, but keep this field non-null
    context.setUserId(UserGroupInformation.getCurrentUser().getShortUserName());
    // Use app ID to generate a default flow name for orphan app
    context.setFlowName(
        TimelineUtils.generateDefaultFlowNameBasedOnAppId(appId));
    // Set the flow version to string 1 if it's an orphan app
    context.setFlowVersion("1");
    // Set the flow run ID to 1 if it's an orphan app
    context.setFlowRunId(1L);
    context.setAppId(appId.toString());
{code}

The flow name, version, and the run id may be overridden if the application 
sets the YARN tag.

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

Reply via email to