[
https://issues.apache.org/jira/browse/YARN-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14367546#comment-14367546
]
Hitesh Shah commented on YARN-2375:
-----------------------------------
[~jeagles] just pointed me to this jira.
Firstly, this seems like an incompatible change for 2.6.0.
Second, the semantics of the property "yarn.timeline-service.enabled" have
changed. Earlier, this seemed like a global/admin flag at the YARN level that
controlled whether ATS was enabled or disabled. Now, it seems like the
assumption is that every application framework needs to check a YARN property
config before deciding to use ATS or not?
There is also an inconsistency in how YarnClient behaves as compared to
TimelineClient. YarnClient obeys the yarn.timeline-service.enabled flag. But,
TimelineClient does not.
[~zjshen] [~jeagles] [~vinodkv] [~mitdesai] Comments?
> Allow enabling/disabling timeline server per framework
> ------------------------------------------------------
>
> Key: YARN-2375
> URL: https://issues.apache.org/jira/browse/YARN-2375
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Jonathan Eagles
> Assignee: Mit Desai
> Fix For: 2.7.0, 2.6.1
>
> Attachments: YARN-2375.1.patch, YARN-2375.patch, YARN-2375.patch,
> YARN-2375.patch, YARN-2375.patch
>
>
> This JIRA is to remove the ats enabled flag check within the
> TimelineClientImpl. Example where this fails is below.
> While running secure timeline server with ats flag set to disabled on
> resource manager, Timeline delegation token renewer throws an NPE.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
