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

Robert Joseph Evans commented on MAPREDUCE-4365:
------------------------------------------------

Jie,

I am confused too.  Do you want to profile the task or the task tracker?  If 
you want to profile the task you can do a combination of what I said and what 
Arun is saying.

{noformat}
hadoop jar ... -Dmapred.map.child.java.opts="... -agentlib:yjpagent" 
-Dmapred.reduce.child.java.opts="... -agentlib:yjpagent" 
-Dmapred.child.env="... LD_LIBRARY_PATH=yourkit/bin/linux-x86-32" -archive 
'/path/to/yourkit.tgz#yourkit' ...
{noformat}

This is just thrown together from memory and from 
http://www.yourkit.com/docs/80/help/agent.jsp so some of the parameter options 
may be wrong, but it should point you down the correct path.
                
> Shipping Profiler Libraries by DistributedCache
> -----------------------------------------------
>
>                 Key: MAPREDUCE-4365
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4365
>             Project: Hadoop Map/Reduce
>          Issue Type: New Feature
>    Affects Versions: 1.0.3
>            Reporter: Jie Li
>
> Hadoop profiling is great for performance tuning and debugging, but currently 
> we can only use Java built-in profilers such as HProf, and for other 
> profilers we need to install them on all slave nodes first, which is 
> inconvenient for large clusters and sometimes impossible for production 
> clusters. 
> Supporting shipping profiler libraries using DistributedCache will solve this 
> problem. For example, in mapred.task.profile.params, we specify a profiler 
> library from the DistributedCache using special place holders such as 
> <foo.jar>, and Hadoop can look at the DistributedCache to replace <foo.jar> 
> with the localized path before launching the child jvm.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to