[
https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010172#comment-15010172
]
Naganarasimha G R commented on YARN-4356:
-----------------------------------------
Yes [~varun_saxena], i agree that the approach which is taken for enabling
ATSv1 and ATSv2 is bit shaky, but we had discussed about supporting version in
YARN-3034 and many of initial patches there were based on version but later
[~zjshen] had informed in the
[comment|https://issues.apache.org/jira/browse/YARN-3034?focusedCommentId=14376575&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14376575]
not to create version based configuration and to handle based on old config
and new config to identify the old version and the new version. May be assuming
that ATSv1 will be replaced by V2 with complete compatability. But definetely
it requires overhaul which i plan to do as part of YARN-3623.
> ensure the timeline service v.2 is disabled cleanly and has no impact when
> it's turned off
> ------------------------------------------------------------------------------------------
>
> Key: YARN-4356
> URL: https://issues.apache.org/jira/browse/YARN-4356
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Assignee: Sangjin Lee
> Priority: Critical
> Labels: yarn-2928-1st-milestone
>
> For us to be able to merge the first milestone drop to trunk, we want to
> ensure that once disabled the timeline service v.2 has no impact from the
> server side to the client side. If the timeline service is not enabled, no
> action should be done. If v.1 is enabled but not v.2, v.1 should behave the
> same as it does before the merge.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
