Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Wed, 18 Nov 2015 03:55:11 +0000 (UTC)
From: "Naganarasimha G R (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12828985.1431381348000.101623.1447818911136@Atlassian.JIRA>
In-Reply-To: <JIRA.12828985.1431381348000@Atlassian.JIRA>
References: <JIRA.12828985.1431381348000@Atlassian.JIRA>
 <JIRA.12828985.1431381348127@arcas>
Subject: [jira] [Commented] (YARN-3623) Having the config to indicate the
 timeline service version
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

I would like to handle this jira once Version config is pushed in as part of 1.5.

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