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

Naganarasimha G R commented on YARN-4183:
-----------------------------------------

Hi [~sjlee0], [~djp] & [~xgong], Now that YARN-3623 is in, can we decide on 
this ? Whether we need to introduce another configuration to decide whether 
client delegation tokens are required to be fetched  along with the existing 
configuration (timeline service and security is enabled ) ? or is it sufficient 
that clients can configure {{yarn.timeline-service.client.best-effort}} / 
{{yarn.timeline-service.enabled}} to false 

> 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