You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Nigel Daley (JIRA)" <ji...@apache.org> on 2008/01/29 02:07:33 UTC

[jira] Assigned: (HADOOP-2723) Hadoop 2367- Does not respect JobConf.getProfileEnabled()

     [ https://issues.apache.org/jira/browse/HADOOP-2723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nigel Daley reassigned HADOOP-2723:
-----------------------------------

    Assignee: Amareshwari Sri Ramadasu

Amareshwari, please evaluate asap to determine if this is a 0.16 blocker.

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