Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Mon, 28 Oct 2013 22:56:31 +0000 (UTC)
From: "Aniket Mokashi (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: <JIRA.12676237.1383000785314.14480.1383000991013@arcas>
In-Reply-To: <JIRA.12676237.1383000785314@arcas>
References: <JIRA.12676237.1383000785314@arcas>
Subject: [jira] [Updated] (PIG-3549) Print hadoop jobids for failed, killed
 job
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/PIG-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aniket Mokashi updated PIG-3549:
--------------------------------

    Attachment: PIG-3549.patch

Initial attempt to solve this.

> Print hadoop jobids for failed, killed job
> ------------------------------------------
>
>                 Key: PIG-3549
>                 URL: https://issues.apache.org/jira/browse/PIG-3549
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.12.0
>            Reporter: Aniket Mokashi
>             Fix For: 0.12.1
>
>         Attachments: PIG-3549.patch
>
>
> It would be better if we dump the hadoop job ids for failed, killed jobs in pig log. Right now, log looks like following-
> {noformat}
> ERROR org.apache.pig.tools.grunt.Grunt: ERROR 6017: Job failed! Error - NA
> INFO org.apache.pig.backend.hadoop.executionengine.mapReduceLayer.MapReduceLauncher: Job job_pigexec_1 killed
> {noformat}
> From that its hard to say which hadoop job failed if there are multiple jobs running in parallel.


--
This message was sent by Atlassian JIRA
(v6.1#6144)