accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Srinivasan <james.sriniva...@gmail.com>
Subject Re: Virtual Classpath Issue [SEC=UNOFFICIAL]
Date Mon, 16 Sep 2019 05:02:09 GMT
I can't tell without the full stack trace, but we had an issue when
tmpwatch cleaned up /tmp which was where the VFS classloader cached jars by
default. Might that be your issue?

On Mon, 16 Sep 2019, 04:02 Dickson, Matt MR, <matt.dickson@defence.gov.au>
wrote:

>
>
> *UNOFFICIAL *
>
> I have a question about Accumulo and classloading.  We have an iterator
> that does not run very often, sometimes 1 week might go by without it
> running.  When it does run after a period of inactivity we get an exception:
>
>
>
> Java.lang.ClassNotFoundException: …BlahIterator
>
> at
> org.apache.commons.vfs2.impl.VFSClassLoader.findClass(VFSClassLoader.java:184)
>
> …
>
> Caused by:
> org.apache.commons.vfs2.provider.DefaultFileContent.getAttributes(DefaultFileContent.java:257)
>
> …
>
> Caused by: java.lang.NullPointerException
>
>                 at
> org.apache.commons.vfs2.provider.jar.JarFileSystem.getAttributes(JarFileSystem:91)
>
> …
>
>
>
> It looks as though the class is aged out of a cache, but then fails to
> load it back into the cache for some reason.  The classes are all located
> in HDFS and we did not get this problem before moving to a virtual
> classpath (VFS).  The classes used to be local on each tablet server.
>
>
>
> Is there some way to stop it unloading the class from the cache?  The only
> way we have to fix this right now is to re-start Accumulo across the whole
> cluster.
>
>
>
>
>

Mime
View raw message