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

Sangjin Lee commented on YARN-3623:
-----------------------------------

I agree the rolling upgrade use case from v.1 to v.2 should be addressed. We 
had some offline discussion on this too. Since it is a pretty major item in and 
of itself and somewhat separate (being v.2-specific) from this specific JIRA, 
it may be sufficient to note it here and carry on that discussion on a v.2 
subtask. Sound good?

I'm fine with the current name "yarn.timeline-service.version". I just want to 
clarify the interpretation of this config on the cluster side and on the client 
side.

On the cluster side, it *should* always be interpreted as precisely which 
version of the timeline service should be up. If 
"yarn.timeline-service.version" is 1.5, and "yarn.timeline-service.enabled" is 
true, it should be understood as the cluster should bring up the timeline 
service v.1.5 (and nothing else), and the client can expect that to be the case.

On the client side, clearly a client that uses the same version should expect 
to succeed. If a client chooses to use a smaller version in spite of this, then 
depending on how robust the compatibility story is between versions, the 
results may vary (part of the rolling upgrade discussion included).

> We should have a config to indicate the Timeline Service version
> ----------------------------------------------------------------
>
>                 Key: YARN-3623
>                 URL: https://issues.apache.org/jira/browse/YARN-3623
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: timelineserver
>            Reporter: Zhijie Shen
>            Assignee: Xuan Gong
>         Attachments: YARN-3623-2015-11-19.1.patch
>
>
> 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