Return-Path: X-Original-To: apmail-crunch-dev-archive@www.apache.org Delivered-To: apmail-crunch-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A304F10A95 for ; Sat, 22 Feb 2014 17:33:22 +0000 (UTC) Received: (qmail 63844 invoked by uid 500); 22 Feb 2014 17:33:21 -0000 Delivered-To: apmail-crunch-dev-archive@crunch.apache.org Received: (qmail 63763 invoked by uid 500); 22 Feb 2014 17:33:21 -0000 Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@crunch.apache.org Delivered-To: mailing list dev@crunch.apache.org Received: (qmail 63750 invoked by uid 500); 22 Feb 2014 17:33:20 -0000 Delivered-To: apmail-incubator-crunch-dev@incubator.apache.org Received: (qmail 63695 invoked by uid 99); 22 Feb 2014 17:33:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Feb 2014 17:33:20 +0000 Date: Sat, 22 Feb 2014 17:33:20 +0000 (UTC) From: "Josh Wills (JIRA)" To: crunch-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CRUNCH-353) MRPipeline exits immediately when job failure is noticed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CRUNCH-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13909449#comment-13909449 ] Josh Wills commented on CRUNCH-353: ----------------------------------- Cool, +1. > MRPipeline exits immediately when job failure is noticed > -------------------------------------------------------- > > Key: CRUNCH-353 > URL: https://issues.apache.org/jira/browse/CRUNCH-353 > Project: Crunch > Issue Type: Bug > Components: Core > Affects Versions: 0.9.0, 0.8.2 > Reporter: Chao Shi > Assignee: Chao Shi > Attachments: crunch-353.patch > > > The current behavior is to wait for all running job complete. A trivial patch is attached to solve this issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)