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 Thu, 19 Nov 2015 01:09:11 GMT

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

Sangjin Lee commented on YARN-4183:

bq. But along with this i think we need to start the timelineservice daemon only if yarn.timeline-service.enabled
is set to true. This will double ensure that the configurations are done properly. But might
have compatability issues. Thoughts?

I think that would be a good sanity check. I'm honestly not 100% clear on what interpretation
is considered compatible and what not when it comes to configuration. Understanding yarn.timeline-service.enabled
implies the server-side timeline service daemons should be up and using it that way seems
within the limits of the current understanding. Those who have better understanding on the
compatibility, could you comment? What scenarios could be worrisome?

bq. I was wondering what should be the default value so that it doesnt break the compatability
with existing apps, i presume it should be true to get the same behavior as of now ?

Yes if changing the default is considered incompatible. Then again, I'm not 100% certain.

> Enabling generic application history forces every job to get a timeline service delegation
> ------------------------------------------------------------------------------------------------
>                 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

View raw message