Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 18 Dec 2014 21:47:15 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12759702.1417794709000.61689.1418939235179@Atlassian.JIRA>
In-Reply-To: <JIRA.12759702.1417794709000@Atlassian.JIRA>
References: <JIRA.12759702.1417794709000@Atlassian.JIRA>
 <JIRA.12759702.1417794709082@arcas>
Subject: [jira] [Commented] (ACCUMULO-3383) AccumuloVFSClassloader creates
 conflicting local cache directory names when vfs.cache.dir property is set.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-3383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252342#comment-14252342 ] 

Christopher Tubbs commented on ACCUMULO-3383:
---------------------------------------------

I was able to get an answer: these are cleaned up when the JVM exists, normally. I'll go ahead and apply the patch.

> 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
>            Reporter: Drew Farris
>            Assignee: Drew Farris
>            Priority: Minor
>             Fix For: 1.7.0, 1.6.3
>
>         Attachments: ACCUMULO-3383-1.patch, ACCUMULO-3383.patch
>
>
> 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)