accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Drew Farris (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-3383) AccumuloVFSClassloader creates conflicting local cache directory names when vfs.cache.dir property is set.
Date Fri, 05 Dec 2014 15:52:12 GMT
Drew Farris created ACCUMULO-3383:
-------------------------------------

             Summary: AccumuloVFSClassloader creates conflicting local cache directory names
when vfs.cache.dir property is set.
                 Key: ACCUMULO-3383
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3383
             Project: Accumulo
          Issue Type: Bug
          Components: start
    Affects Versions: 1.6.1, 1.7.0, 2.0.0
            Reporter: Drew Farris
            Assignee: Drew Farris
            Priority: Minor


When the vfs.cache.dir property is not set, the AccumuloVFSClassloader will use java.io.tmpdir
as a base directory for the local cache of jars and then generate a unique directory name
using a combination of the processid, hostname and userid executing the JVM.

When the vfs.cache.dir property is set, that value is used as the base directory and  an attempt
to generate a unique directory is made using an AtomicInteger. This isn't suitable because
for non-long lived processes, this will always be 1 - and there's a good chance that directory
already exists and is owned by another user, and not writable to by the user in question.


This leads to a failure of the invoked accumulo component to start.

Modify the behavior of the unique directory creation when vfs.cache.dir is set so that it
employs the same mechanism for unique directory naming that is used when it is not set.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message