You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/01/11 01:16:56 UTC

[jira] [Resolved] (ACCUMULO-2174) VFS Classloader has potential to collide localized resources

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

Josh Elser resolved ACCUMULO-2174.
----------------------------------

    Resolution: Fixed

Include process name in the temporary direction used.

> VFS Classloader has potential to collide localized resources
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-2174
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2174
>             Project: Accumulo
>          Issue Type: Bug
>          Components: start
>    Affects Versions: 1.5.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.5.1, 1.6.0
>
>
> Looking through the VFS implementation, a single directory is used for *all* Accumulo processes on a single host for a given user.
> Commons-vfs makes some attempt (adds a number to the localized resource, created from a random number between 0 and 2**16, and incremented for each updated resource) to give a "unique" resource. Rather than let this bite us later on, it's rather simple for us to just query the runtime and get the pid of the process to add into the temp directory that a process uses.
> This could increase the copies of resources per host (by the number of processes), but I think the performance penalty is much better than suddenly getting someone else's jars in the middle of my process execution.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)