[
https://issues.apache.org/jira/browse/MAPREDUCE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400488#comment-13400488
]
Robert Joseph Evans commented on MAPREDUCE-4365:
------------------------------------------------
Why can't you just use specify your distributed cache entry with something like
hdfs://path/to/profiler.lib#profiler-link.lib? I know it is a little ugly but
it will add a symbolic name link named profiler-link.lib in the current working
directory of your task to wherever it is in the distributed cache.
You can do this to with a tgz or zip.
hdfs://path/to/archive.tgz#profiler
Now if you want to access lib/profiler.so from inside of archive.tgz you would
use a path of profiler/lib/profiler.so.
> 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
