Varun Saxena commented on YARN-4356:

That's quite a comprehensive list.

I was wondering if we should relook at some of our configurations.
For instance, in RM for ATSv1, we were publishing system metrics if timeline 
service was enabled and system metrics publishing was also *enabled*
Now we publish to ATSv2 if timeline service is enabled and system metrics 
publishing is *disabled*

This doesn't sound semantically correct to me and can be quite confusing for 
the end user as well.
Maybe we can use the timeline service version config introduced in YARN-4234.

> 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

Reply via email to