[
https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15051377#comment-15051377
]
Li Lu commented on YARN-3623:
-----------------------------
I'd like to make sure I understand this change correctly. Specifically, what
kind of new cases do we allow by removing the "nothing else" part. IIUC, this
allows us to bring up an old ATS server after the system has been upgraded.
This looks fine with me. Am I missing some other cases introduced by this
change?
> 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: New Feature
> Components: timelineserver
> Reporter: Zhijie Shen
> Assignee: Xuan Gong
> Fix For: 2.8.0
>
> Attachments: YARN-3623-2015-11-19.1.patch,
> YARN-3623-2015-12-09.patch, YARN-3623-addendum.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)
