Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 3 May 2013 16:02:15 +0000 (UTC)
From: "Keith Turner (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12643281.1366305564400.265815.1367596935908@arcas>
In-Reply-To: <JIRA.12643281.1366305564400@arcas>
References: <JIRA.12643281.1366305564400@arcas>
Subject: [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Keith Turner commented on ACCUMULO-1321:
----------------------------------------

bq. The original issue we're working around - that different references to different versions get held onto in the VFS (I believe that was the issue)

I am not sure if this a VFS issue or if we were using it improperly.  Maybe a question on their mailing list?

I asked a question about the collision behavior and have not seen an answer to that.  Maybe that should be a ticket.

http://markmail.org/thread/nmk5k3gp5a4ptuls

Also if the DefaultFilesystemManager does not have a finalize, that may be worth a ticket.

                
> Dynamic Classloader lost jars
> -----------------------------
>
>                 Key: ACCUMULO-1321
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1321
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: John Vines
>            Assignee: Keith Turner
>            Priority: Blocker
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-1321.patch
>
>
> We have a table setup that uses some custom iterators. We ran an MR job against it without issues. We then ran the job immediately after the first one wrapped and 2 of my tservers errored with ClassNotFoundException, even though it ran just fine before.
> Unfortunately we don't have a stack trace (to see if it was breaking differently in the VFSClassLoader), nor a convenient way to recreate currently. We're working on reproducing it in order to get more information.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira