[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005021#comment-15005021
]
Sangjin Lee commented on YARN-4183:
-----------------------------------
{quote}
+1. I don't see a fundamental challenge to support "1", "1.5", and "1, 2" at
the same time. One thing we need to be careful about is the meaning of the
incremental relationships between v1 and v1.5. Having "1.5" in the config means
the server supports ATS v1 API up to v1.5, but having "2" in the config does
not indicate any support to ATS v1?
{quote}
Yes I think that is fine. The key motivation again is to be able to test and
compare 1.x and 2. Also, if 1.5 is meant to include 1, then we can limit
supported values as something like (1, 2), (1.5, 2), etc. but not (1, 1.5).
> Enabling generic application history forces every job to get a timeline
> service delegation token
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-4183
> URL: https://issues.apache.org/jira/browse/YARN-4183
> Project: Hadoop YARN
> Issue Type: Bug
> Affects Versions: 2.7.1
> Reporter: Mit Desai
> Assignee: Mit Desai
> Attachments: YARN-4183.1.patch
>
>
> When enabling just the Generic History Server and not the timeline server,
> the system metrics publisher will not publish the events to the timeline
> store as it checks if the timeline server and system metrics publisher are
> enabled before creating a timeline client.
> To make it work, if the timeline service flag is turned on, it will force
> every yarn application to get a delegation token.
> Instead of checking if timeline service is enabled, we should be checking if
> application history server is enabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
