[
https://issues.apache.org/jira/browse/ACCUMULO-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Vines updated ACCUMULO-1321:
---------------------------------
Attachment: ACCUMULO-1321.patch
This patch creates a secondary vfs for the reloading classloader. The Vfs gets
recreated whenever the classloader does. It uses a different directory
(accumulo-vfs-reloading-cacce instead of accumulo-vfs-cache). I didn't want to
commit it since Keith was also looking into this and I'm still not sure on the
repurcussions of generating new Vfs constantly. However, it does work.
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 too.
> Dynamic Classloader lost jars
> -----------------------------
>
> Key: ACCUMULO-1321
> URL: https://issues.apache.org/jira/browse/ACCUMULO-1321
> Project: Accumulo
> Issue Type: Bug
> Reporter: John Vines
> Assignee: Keith Turner
> 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
