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

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

Hi [~zjshen] & [~sjlee0], Further to the above mentioned scenario, i think it 
was decided we are going to support both V1 along with V2. Earlier IIRC we had 
not gone for V1 and V2 configuration because if in future V1 is removed then 
this configuration will become redundant but based on later discussions we 
decide to have both right ? so shall we get these changes done ?


> Having the config to indicate the timeline service version
> ----------------------------------------------------------
>
>                 Key: YARN-3623
>                 URL: https://issues.apache.org/jira/browse/YARN-3623
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Zhijie Shen
>
> So far RM, MR AM, DA AM added/changed new config to enable the feature to 
> write the timeline data to v2 server. It's good to have a YARN 
> timeline-service.version config like timeline-service.enable to indicate the 
> version of the running timeline service with the given YARN cluster. It's 
> beneficial for users to more smoothly move from v1 to v2, as they don't need 
> to change the existing config, but switch this config from v1 to v2. And each 
> framework doesn't need to have their own v1/v2 config.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to