[
https://issues.apache.org/jira/browse/PIG-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12874269#action_12874269
]
Daniel Dai commented on PIG-1343:
---------------------------------
In this case hadoop does not give a meaningful message in
MapReduceLauncher:282, backendException is null. But take a look why in "dump",
this "null backendException" actually trigger a message into pig log, but in
"store", Pig silently stop without a trace.
> pig_log file missing even though Main tells it is creating one and an M/R job
> fails
> ------------------------------------------------------------------------------------
>
> Key: PIG-1343
> URL: https://issues.apache.org/jira/browse/PIG-1343
> Project: Pig
> Issue Type: Bug
> Components: impl
> Affects Versions: 0.6.0
> Reporter: Viraj Bhat
> Assignee: Ashitosh Darbarwar
> Attachments: PIG-1343-1.patch
>
>
> There is a particular case where I was running with the latest trunk of Pig.
> {code}
> $java -cp pig.jar:/home/path/hadoop20cluster org.apache.pig.Main testcase.pig
> [main] INFO org.apache.pig.Main - Logging error messages to:
> /homes/viraj/pig_1263420012601.log
> $ls -l pig_1263420012601.log
> ls: pig_1263420012601.log: No such file or directory
> {code}
> The job failed and the log file did not contain anything, the only way to
> debug was to look into the Jobtracker logs.
> Here are some reasons which would have caused this behavior:
> 1) The underlying filer/NFS had some issues. In that case do we not error on
> stdout?
> 2) There are some errors from the backend which are not being captured
> Viraj
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
