hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof can cause JobClient to report job failure
Date Wed, 21 Oct 2009 23:20:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768512#action_12768512
] 

Todd Lipcon commented on MAPREDUCE-1131:
----------------------------------------

Oops - I was thrown by the job name being the same in both cases. You should change the job
name for the second submission, I think.

> 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.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.


Mime
View raw message