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

Sangjin Lee commented on YARN-4356:
-----------------------------------

In order to make progress with this work, I would like to propose the following.

Let's use yarn.timeline-service.enabled = true && yarn.timeline-service.version 
= 2.0 (per YARN-4234) as the test if the timeline service v.2 is enabled both 
on the server side and the client side.

With that check, let's wire off the timeline service v.2 feature as cleanly and 
early as possible. As we said earlier, we can focus on disabling the feature in 
this JIRA (assume a binary behavior for now). We can look at whether we can 
enable both in YARN-4368.

Does it sound like a plan?

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

Reply via email to