[
https://issues.apache.org/jira/browse/YARN-4356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15011604#comment-15011604
]
Li Lu commented on YARN-4356:
-----------------------------
bq. I haven't looked at YARN-4234 in detail yet. Are you referring to the
version config?
Yes.
bq. While I see value in being able to do so, I recognize that it would be a
pretty major rework, as the current code is making a strong assumption of this
being a binary choice (mutually exclusive).
Agreed. Let's move forward with checking all v2 code can be cleanly disabled
here, and see how we can allow two versions running side by side in the other
JIRA?
> 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)
