You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Aniket Mokashi (JIRA)" <ji...@apache.org> on 2014/01/23 06:44:41 UTC
[jira] [Comment Edited] (PIG-2672) Optimize the use of
DistributedCache
[ https://issues.apache.org/jira/browse/PIG-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13879461#comment-13879461 ]
Aniket Mokashi edited comment on PIG-2672 at 1/23/14 5:44 AM:
--------------------------------------------------------------
Another proposal: We create /tmp/$user.name/jarcache with 700 and use it as a user level jarcache. Also, every time a jar is used from jar case we do fs.setTimes(jarpath, now, now) to update atime, mtime of the jar (to avoid cleanups).
[~rohini] thoughts?
was (Author: aniket486):
Another proposal: We create /tmp/${user.name}/jarcache with 700 and use it as a user level jarcache. Also, every time a jar is used from jar case we do fs.setTimes(jarpath, now, now) to update atime, mtime of the jar (to avoid cleanups).
[~rohini] thoughts?
> Optimize the use of DistributedCache
> ------------------------------------
>
> Key: PIG-2672
> URL: https://issues.apache.org/jira/browse/PIG-2672
> Project: Pig
> Issue Type: Improvement
> Reporter: Rohini Palaniswamy
> Fix For: 0.13.0
>
> Attachments: PIG-2672-5.patch, PIG-2672.patch
>
>
> Pig currently copies jar files to a temporary location in hdfs and then adds them to DistributedCache for each job launched. This is inefficient in terms of
> * Space - The jars are distributed to task trackers for every job taking up lot of local temporary space in tasktrackers.
> * Performance - The jar distribution impacts the job launch time.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)