[ 
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943832#comment-14943832
 ] 

Jonathan Eagles commented on YARN-4183:
---------------------------------------

[~xgong], this issue is two-fold. 1) The web services publishing should trigger 
posting history based on generic history enablement and not timeline server 
enablement. 2) There is still no separation between timeline clients that 
require delegation tokens and those that don't. See YARN-3942. As a result, if 
timelineservice is enabled at the global level, then each yarn client will get 
a timeline delegation token which makes the timeline service a live dependency. 
Meaning if the timeline service is down, then the grid is down.

This patch above is a clean way to avoid enabling the timeline service for all 
YarnClients in the cluster.

> 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)

Reply via email to