Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0AAF47B22 for ; Tue, 18 Oct 2011 15:17:35 +0000 (UTC) Received: (qmail 92142 invoked by uid 500); 18 Oct 2011 15:17:34 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 92113 invoked by uid 500); 18 Oct 2011 15:17:34 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 92105 invoked by uid 99); 18 Oct 2011 15:17:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 15:17:34 +0000 X-ASF-Spam-Status: No, hits=-2000.5 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 15:17:32 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 9967F30E5AD for ; Tue, 18 Oct 2011 15:17:11 +0000 (UTC) Date: Tue, 18 Oct 2011 15:17:11 +0000 (UTC) From: "Vinod Kumar Vavilapalli (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1348410376.6673.1318951031629.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <800380816.37669.1316225288868.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3028) Support job end notification in .next /0.23 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/MAPREDUCE-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129789#comment-13129789 ] Vinod Kumar Vavilapalli commented on MAPREDUCE-3028: ---------------------------------------------------- No, I'd not put this in YARN (i.e Nodemanager). The notification is currently a MapReduce only feature (atleast it seems to be for now). I can imagine a generic application finish notification from YARN itself (RM or NM), but I'd postpone any discussion about that if we can pull it off in MapReduce AM for now. Also 30secs seems way too much, even if it for that one job. Make it something in the order of 5s of seconds? > Support job end notification in .next /0.23 > ------------------------------------------- > > Key: MAPREDUCE-3028 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3028 > Project: Hadoop Map/Reduce > Issue Type: Bug > Reporter: Mohammad Kamrul Islam > Assignee: Ravi Prakash > Priority: Blocker > Fix For: 0.23.0 > > > Oozie primarily depends on the job end notification to determine when the job finishes. In the current version, job end notification is implemented in job tracker. Since job tracker will be removed in the upcoming hadoop release (.next), we wander where this support will move. I think this best effort notification could be implemented in the new Application Manager as one of the last step of job completion. > Whatever implementation will it be, Oozie badly needs this feature to be continued in next releases as well. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira