accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
Date Mon, 29 Apr 2013 23:58:15 GMT


John Vines commented on ACCUMULO-1321:

Yeah, there are a few options. Unique dirs per vfs will help with the potential for collision,
but then we need to make sure that the different cache dirs don't collide. And that doesn't
help with the cruft which would be generated. I would be a lot more comfortable if we can
find a way to have a vfs that cleans up when there are no more accesses to it. Keith had mentioned,
possibly in irc, about utilizing an extended VFS which has a final method to call close on
itself to make sure things get tidied up.
> Dynamic Classloader lost jars
> -----------------------------
>                 Key: ACCUMULO-1321
>                 URL:
>             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:

View raw message