Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1905309944.1257402693420.JavaMail.jira@brutus>
Date: Thu, 5 Nov 2009 06:31:33 +0000 (UTC)
From: "Vinod K V (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1131) Using profilers other than hprof
 can cause JobClient to report job failure
In-Reply-To: <1422187703.1256165219529.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod K V commented on MAPREDUCE-1131:
--------------------------------------

Sorry for coming late on this. But I think the profile file is originally intended only when hprof is in use, and that to when the 'file' argument is passed .So, instead of adding another configuration, why not downloadProfile() *only* when hprof is in use and only when the file argument is non-null? This includes parsing the profile-params configuration, of course.

Or do you expect such file to be generated with other profilers too?

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