hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zhijie Shen (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 18:00:43 GMT

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

Zhijie Shen commented on YARN-3144:
-----------------------------------

bq. How do we know if the job has used the service if we're trying to get the delegation token?

I guess it's reasonable for the job submitter to know if the app is using the timeline service
or not (such as Tez), and putting data to the timeline server is enabled or not. I meant the
decision of whether loading the timeline DT automatically can be on job basis.

But Jonathan's case about Oozie workflow makes sense. Different apps in a workflow may even
have different situation of using the timeline service.

bq. My main purpose now is to given users options on whether the timeline server failures
are fatal to the users job.

Given the justification above, it sounds reasonable. Hopefully it's could just be a temporal
solution before high availability of the timeline service.


> 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