accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1321) Dynamic Classloader lost jars
Date Mon, 29 Apr 2013 20:38:16 GMT


Keith Turner commented on ACCUMULO-1321:

Some notes on the code I found in VFS.  As I look more closely at this code, the behavior
my be slightly different than what I described in my previous post.

  * o.a.c.vfs2.provider.jar.JarFileProvider extends
extends o.a.c.vfs2.provider.AbstractLayeredFileProvider
  * o.a.c.vfs2.provider.AbstractLayeredFileProvider.createFileSystem() will look in a cache
(this is a protected cache, not the one specified by the user).  This is the function that
will return a cached JarFileSystem.
  * will place objects
into another cache (the cache specified by the user).  These could age off, which may result
in different behavior than I described above.  Need to look into this further.

> Dynamic Classloader lost jars
> -----------------------------
>                 Key: ACCUMULO-1321
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: John Vines
>            Assignee: Keith Turner
>             Fix For: 1.5.0
> 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