[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15005342#comment-15005342
]
Varun Saxena commented on YARN-4183:
------------------------------------
bq. i feel yarn.resourcemanager.system-metrics-publisher.enabled is sufficient
to be configured.
Agree. Enabling system metrics publisher should be considered to be enough to
publish events from RM.
bq. As far as i view it "yarn.timeline-service.enabled"* name is misleading, it
should be more to signify client requires the timeline service's delegation
token.
Maybe we can use the version config to decide if we have to fetch a token or
not (in addition with timeline service enabled config ?).
> 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)
