[
https://issues.apache.org/jira/browse/YARN-3623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036654#comment-15036654
]
Li Lu commented on YARN-3623:
-----------------------------
Hi [~Naganarasimha] sorry for the late reply (just came back from a vacation).
Plan sounds good to me. One thing is that we may not need to mark this JIRA as
ATS v1.5 since the fix here is a rather general one: from v1.5 on we need to
handle this configuration in ATS correctly, thus I think it'll be a general
JIRA and not attached with any specific version of ATS. Right now we have the
patch for this JIRA so we can proceed with the rest of the plan? It will
certainly be helpful if anyone has any concerns on Naga's plan.
> 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: Naganarasimha G R
> 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)
