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 21:08:15 GMT


Keith Turner commented on ACCUMULO-1321:

[~vines] I will take a look at the patch.   

bq. Another question is the old vfs when it reloads.  We can attempt to close it, but that
may cause issues for things in mid-reference, so we may need to put more resilience in that

Yeah I think about what you said about things in mid-reference is correct.  Basically, an
old classloader using an old vfs instance could be in use for an indeterminable time period.
 The question is when everything stops referencing the old vfs, will java gc clean it properly.

> 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