hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-4183) Enabling generic application history forces every job to get a timeline service delegation token
Date Tue, 10 Nov 2015 23:15:11 GMT

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

Naganarasimha G R commented on YARN-4183:

Oops, Missed this comment [~sjlee0],

Documentation gives a fair idea and its same as per my understanding, 
*yarn.timeline-service.enabled* : Indicate to clients whether timeline service is enabled
or not. If enabled, clients will put entities and events to the timeline server.

*yarn.timeline-service.generic-application-history.enabled* : Indicate to clients whether
to query generic application data from timeline history-service or not. If not enabled then
application data is queried only from Resource Manager. Defaults to false. (which is currently
not there in documentation but present in TimelineServer.MD)

*yarn.resourcemanager.system-metrics-publisher.enabled* : The setting that controls whether
yarn system metrics is published on the timeline server or not by RM. (This requires yarn.timeline-service.enabled
to be enabled which requires a doc update).

AHS on timelinestore is started if started if "YarnConfiguration.APPLICATION_HISTORY_STORE"
is not configured.

> 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
>             Fix For: 3.0.0, 2.8.0, 2.7.2
>         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