[
https://issues.apache.org/jira/browse/HADOOP-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563412#action_12563412
]
amareshwari edited comment on HADOOP-2723 at 1/28/08 11:23 PM:
----------------------------------------------------------------------------
Yes. It seems like a blocker. We should add the guard in taskRunner.run() .
was (Author: amareshwari):
Yes. It seems like a blocker. We should the guard in taskRunner.run() .
> Hadoop 2367- Does not respect JobConf.getProfileEnabled()
> ---------------------------------------------------------
>
> Key: HADOOP-2723
> URL: https://issues.apache.org/jira/browse/HADOOP-2723
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: hudson
> Reporter: Clint Morgan
> Assignee: Amareshwari Sri Ramadasu
> Priority: Blocker
> Fix For: 0.16.0
>
>
> Looks like it should add a guard in TaskRunner.run()
> if (conf.getProfileEnabled()) {
> if (conf.getProfileTaskRange(t.isMapTask()
> ).isIncluded(t.getPartition())) {
> File prof = TaskLog.getTaskLogFile(taskid, TaskLog.LogName.PROFILE);
>
> vargs.add("-agentlib:hprof=cpu=samples,heap=sites,force=n,thread=y,"+
> "verbose=n,file="+prof.toString());
> }
> }
> Also, how come these conf values were not added to hadoop-default.xml?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
