hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sangjin Lee (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token
Date Mon, 14 Dec 2015 21:59:46 GMT

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

Sangjin Lee commented on YARN-4183:
-----------------------------------

IMO it is probably acceptable for clients to set yarn.timeline-service.enabled (and yarn.timeline-service.client.best-effort?)
to false. If we add a new configuration, I think it should be more along the line of "participate
in the timeline service functionality" rather than specifically about the delegation token.
My understanding is that the YARN client just does not want to do anything with the timeline
service in this case, right?

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

Mime
View raw message