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) Clarify the behavior of timeline service config properties
Date Fri, 01 Apr 2016 03:12:25 GMT

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

Naganarasimha G R commented on YARN-4183:

Thanks for the reveiw and commit [~sjlee0], and reviews from [~jeagles],[~mitdesai],[~xgong],[~vinodkv],[~gtCarrera9]
& [~varun_saxena].
I will cross check for 2.6 branch in a while.

> 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
>             Fix For: 2.8.0, 2.7.3, 2.9.0
>         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

View raw message