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

Rohini Palaniswamy commented on PIG-3035:
-----------------------------------------

In Launcher.java getErrorMessages(), the TaskReport reports[] gives the first 
element as the actual stacktrace and the second one as "Container killed by the 
ApplicationMaster". The parsing logic to construct StackTrace out of the error 
message has an issue, so it fails to construct the Exception and the message 
from the last TaskReport which is Container killed is thrown as error. Fixing 
the logic which constructs the Exception fixes the issue. 

{code}
if(items.length > 0) {
            fileName = items[0];
            lineNumber = Integer.parseInt(items[1]);
        }
{code} 

   items.length is 1 in case of "at 
java.security.AccessController.doPrivileged(Native Method)" in the stack trace 
which does not have a line number. 
                
> With latest version of hadoop23 pig does not return the correct exception 
> stack trace from backend
> --------------------------------------------------------------------------------------------------
>
>                 Key: PIG-3035
>                 URL: https://issues.apache.org/jira/browse/PIG-3035
>             Project: Pig
>          Issue Type: Bug
>    Affects Versions: 0.10.0, 0.11
>            Reporter: Rohini Palaniswamy
>            Assignee: Rohini Palaniswamy
>             Fix For: 0.11, 0.10.1, 0.12
>
>
> With latest version of hadoop, the job failure shown to user is always 
> Container killed by the ApplicationMaster. For eg: 
> "Backend error : Unable to recreate exception from backed error: 
> AttemptID:attempt_1352163563357_0002_m_000000_1 Info:Container killed by the 
> ApplicationMaster"
> Steps to Reproduce:
>   Change hadoop version from 2.0.0-alpha to 0.23.5-SNAPSHOT. Tests 
> TestScalarAliases.testScalarErrMultipleRowsInInput, 
> TestEvalPipeline2.testNonStandardData will fail.   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to