[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997267#comment-14997267
]
Sangjin Lee commented on YARN-4183:
-----------------------------------
Sorry I missed this one as well.
Maybe this is a FAQ somewhere, but what are the relationships among the
following 3 settings?
# yarn.timeline-service.enabled
# yarn.timeline-service.generic-application-history.enabled
# yarn.resourcemanager.system-metrics-publisher.enabled
Can (1) and (2) be set independently, or does setting one have an implication
on the other? How about (3)?
>From the v.2 perspective, there is no separate "generic application history
>service" any way, and we will have to handle this problem in a different
>manner.
> 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
> Fix For: 3.0.0, 2.8.0, 2.7.2
>
> 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)
