[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Naganarasimha G R updated YARN-4183:
------------------------------------
Description: Configurations *"yarn.timeline-service.enabled"* and
*"yarn.timeline-service.client.best-effort"* are not captured better. Currently
if the client doesn't want the tokens to be generated for the timeline service
they can set "yarn.timeline-service.enabled" to false and/or
"yarn.timeline-service.client.best-effort" to true so that even if the ATS is
down jobs can continue to get submitted. This functionality is not properly
documented, so as part of this jira we try to document and clarify these
configurations. (was: 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.)
> Clarify the behavior of timeline service config properties
> ----------------------------------------------------------
>
> 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: Naganarasimha G R
> Attachments: YARN-4183.1.patch, YARN-4183.v1.001.patch,
> YARN-4183.v1.002.patch
>
>
> Configurations *"yarn.timeline-service.enabled"* and
> *"yarn.timeline-service.client.best-effort"* are not captured better.
> Currently if the client doesn't want the tokens to be generated for the
> timeline service they can set "yarn.timeline-service.enabled" to false and/or
> "yarn.timeline-service.client.best-effort" to true so that even if the ATS is
> down jobs can continue to get submitted. This functionality is not properly
> documented, so as part of this jira we try to document and clarify these
> configurations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
