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 "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/04/02 20:31:55 UTC

[jira] [Commented] (YARN-3439) RM fails to renew token when Oozie launcher leaves before sub-job finishes

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

Jason Lowe commented on YARN-3439:
----------------------------------

This appears to be caused by YARN-2704.  YARN-2964 tried to fix it but assumed that Oozie launcher jobs will always run for the duration of the sub-jobs.  This is true when the launcher runs a Pig job, but apparently is not true when it runs a standard MapReduce job.

> RM fails to renew token when Oozie launcher leaves before sub-job finishes
> --------------------------------------------------------------------------
>
>                 Key: YARN-3439
>                 URL: https://issues.apache.org/jira/browse/YARN-3439
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Jason Lowe
>            Assignee: Daryn Sharp
>            Priority: Blocker
>
> When the Oozie launcher runs a standard MapReduce job (not Pig) it doesn't linger waiting for the sub-job to finish.  At that point the RM stops renewing delegation tokens for the launcher job which wreaks havoc on the sub-job if the sub-job runs long enough for the tokens to expire.



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