pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aniket Mokashi (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (PIG-2672) Optimize the use of DistributedCache
Date Thu, 23 Jan 2014 05:44:41 GMT

    [ 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)

Mime
View raw message