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:48:11 GMT

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

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

Hi [~xgong],
bq. The value for yarn.timeline-service.enabled only means whether we have ATS daemon or not.
We should not use this configuration to decide whether the job needs to get the ATS DT.
Just went through the references of all  {{yarn.timeline-service.enabled}}  configuration,
and one thing i could understand was, its not used to indicate ATS daemon is started but kind
of looks like client wants to use ATS daemon or not. and matches with the description in the
document *"Indicate to clients whether timeline service is enabled or not. If enabled, clients
will put entities and events to the timeline server."*
Also if the *timelineserver* daemon is started it directly starts  the timelinestore without
checking for the configuration *"yarn.timeline-service.enabled"*
So its as good as have this configuration if the client wants to put timeline entities else
disable.

> 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
>             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
(v6.3.4#6332)

Mime
View raw message