[
https://issues.apache.org/jira/browse/YARN-4183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220323#comment-15220323
]
Hudson commented on YARN-4183:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #9535 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/9535/])
YARN-4183. Clarify the behavior of timeline service config properties (sjlee:
rev 6d67420dbc5c6097216fa40fcec8ed626b2bae14)
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServer.md
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/resources/yarn-default.xml
> 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)
