Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 18 Dec 2014 21:01:17 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12761893.1418684947000.61169.1418936477183@Atlassian.JIRA>
In-Reply-To: <JIRA.12761893.1418684947000@Atlassian.JIRA>
References: <JIRA.12761893.1418684947000@Atlassian.JIRA>
 <JIRA.12761893.1418684947653@arcas>
Subject: [jira] [Commented] (YARN-2964) RM prematurely cancels tokens for
 jobs that submit jobs (oozie)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jian He commented on YARN-2964:
-------------------------------

bq. We might have had the same issue in this case prior to YARN-2704.
Yes, this is an existing issue. As Robert pointed out in the previous comment, oozie MapReduce sub-job now cannot run beyond 24 hrs. IMO, we can fix this separately ?

> RM prematurely cancels tokens for jobs that submit jobs (oozie)
> ---------------------------------------------------------------
>
>                 Key: YARN-2964
>                 URL: https://issues.apache.org/jira/browse/YARN-2964
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 2.6.0
>            Reporter: Daryn Sharp
>            Assignee: Jian He
>            Priority: Blocker
>         Attachments: YARN-2964.1.patch, YARN-2964.2.patch
>
>
> The RM used to globally track the unique set of tokens for all apps.  It remembered the first job that was submitted with the token.  The first job controlled the cancellation of the token.  This prevented completion of sub-jobs from canceling tokens used by the main job.
> As of YARN-2704, the RM now tracks tokens on a per-app basis.  There is no notion of the first/main job.  This results in sub-jobs canceling tokens and failing the main job and other sub-jobs.  It also appears to schedule multiple redundant renewals.
> The issue is not immediately obvious because the RM will cancel tokens ~10 min (NM livelyness interval) after log aggregation completes.  The result is an oozie job, ex. pig, that will launch many sub-jobs over time will fail if any sub-jobs are launched >10 min after any sub-job completes.  If all other sub-jobs complete within that 10 min window, then the issue goes unnoticed.


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