You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Sangjin Lee (JIRA)" <ji...@apache.org> on 2016/03/30 02:45:25 UTC

[jira] [Commented] (YARN-4183) Clarify the behavior of timeline service config properties

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

Sangjin Lee commented on YARN-4183:
-----------------------------------

I updated the title of the JIRA. Let me know if it is good to go. I'll wait for a couple of hours before committing the patch. Thanks!

> 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
>
>
> 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)