Naganarasimha G R commented on YARN-4183:

[~sjlee0], Sorry missed this comment earlier,
My thoughts are also in line with yours, but just that the documentation is not 
capturing this, Existing :
Indicate to clients whether timeline service is enabled or not. If enabled, 
clients will put entities and events to the timeline server
 i feel we need to capture it as
In the server side it indicates whether timeline service is enabled or not. And 
in the client side, users can enable it to indicate whether they want to use 
timeline service. If enabled in the clientside and security is also enabled, 
then yarn client tries to fetch the delegation tokens for the timeline server.
modifications are welcome
also there {{yarn.timeline-service.client.best-effort}} is wrongly documented 
as {{yarn.timeline-service.best-effort}}. 
So shall i get these things corrected as part of this jira ?

> 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

Reply via email to