[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15018478#comment-15018478
]
Naganarasimha G R commented on YARN-4183:
-----------------------------------------
Thanks for the proposal [~sjlee0],
Only additional query is should the timeline server run if the
{{yarn.timeline-service.enabled}} is enabled ? My opinion would be to have it
so that the configurations is much more stronger, thoughts ?
bq. there needs to be a strong client-side config for each framework (MR or
tez) that controls whether it wants to use the timeline service;
How about the config be
{{yarn.timeline-service.client.require-delegation-token}} or
{{yarn.timeline-service.client.delegation-token.enabled}} ?
bq. I hope the last point should address the original issue of this JIRA
And to further clarify and also as mentioned earlier, there is one more config
{{yarn.timeline-service.client.best-effort}} which will avoid clients to fail
when delegation token fails to be retreived.
> 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)
