You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Aaron Kimball (JIRA)" <ji...@apache.org> on 2009/12/07 22:54:18 UTC
[jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof
can cause JobClient to report job failure
[ https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787141#action_12787141 ]
Aaron Kimball commented on MAPREDUCE-1131:
------------------------------------------
Todd, Vinod --
Do you have thoughts about this version of the patch?
> Using profilers other than hprof can cause JobClient to report job failure
> --------------------------------------------------------------------------
>
> Key: MAPREDUCE-1131
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1131
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: client
> Reporter: Aaron Kimball
> Assignee: Aaron Kimball
> Attachments: MAPREDUCE-1131.2.patch, MAPREDUCE-1131.3.patch, MAPREDUCE-1131.4.patch, MAPREDUCE-1131.5.patch, MAPREDUCE-1131.patch
>
>
> If task profiling is enabled, the JobClient will download the {{profile.out}} file created by the tasks under profile. If this causes an IOException, the job is reported as a failure to the client, even though all the tasks themselves may complete successfully. The expected result files are assumed to be generated by hprof. Using the profiling system with other profilers will cause job failure.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.