hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3144) Configuration for making delegation token failures to timeline server not-fatal
Date Thu, 05 Feb 2015 01:30:34 GMT

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

Jonathan Eagles commented on YARN-3144:
---------------------------------------

While I agree that it eventually will be a necessary serviceat all times. In the case of a
dual history writer in the transition from Mapreduce history and timeline, you are increasing
instability for jobs. This allows users to evaluate the timeline history server without introducing
instability. 

> Configuration for making delegation token failures to timeline server not-fatal
> -------------------------------------------------------------------------------
>
>                 Key: YARN-3144
>                 URL: https://issues.apache.org/jira/browse/YARN-3144
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>         Attachments: YARN-3144.1.patch
>
>
> Posting events to the timeline server is best-effort. However, getting the delegation
tokens from the timeline server will kill the job. This patch adds a configuration to make
get delegation token operations "best-effort".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message