hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3623) We should have a config to indicate the Timeline Service version
Date Thu, 10 Dec 2015 17:00:13 GMT

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

Junping Du commented on YARN-3623:
----------------------------------

bq. "it means the cluster will and should bring up the timeline service v.1.5 (and nothing
else)." 
Think over it again. I am still uncomfortable for the description - "(and nothing else)."
It could be against for our possible solutions for YARN-4368. I prefer to remove this in an
addendum patch or it could provide unnecessary restrictions if it get released in 2.8.0. Thoughts?

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

Mime
View raw message