[
https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787439#action_12787439
]
Vinod K V commented on MAPREDUCE-1131:
--------------------------------------
Also, now that the patch needs some update, can you also add a positive test to
verify success with hprof? We can then also verify that profile files named
like {{$attempt-id.profile}} are indeed download by the JobClient when hprof(by
default) is used.
> 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.
