I'm trying to get vfs loading of my jar working in 1.7.2. On a test cluster of the same version this works fine and I see the jar being replicated in the cache in '/tmp/accumulo-vfs*/fstore-filters-1.3.2.jar', but when I do the exact same thing on prod, I get the stacktrace below. Any ideas?
Setup I used:
config -s general.vfs.context.classpath.fstore=hdfs://nameservice1/libs/accumulo/fstore/.*jar
It looks like the error is when vfs tries to create a temporary file in your tmpdir. I would check that your java.io.tmpdir points to a directory that exists and has the appropriate permissions for the user running the Accumulo process.
Hmm 'jinfo <tabletserver_pid> | grep tmp' shows:
java.io.tmpdir = /tmp
/" shows 777 on /tmp
Grepping for 'tmp' in tserver startup:
[zookeeper.ZooKeeper] INFO : Client environment:java.io.tmpdir=/tmp
[server.Accumulo] INFO : general.vfs.cache.dir = /tmp/accumulo-vfs-cache-accumulo
[server.Accumulo] INFO : tserver.dir.memdump = /tmp
I'm guessing the relevant code to get the dir would be in: AccumuloVFSClassLoader.java
cacheDirPath getAccumuloString(, getProperty());
public static final String VFS_CACHE_DIR = "general.vfs.cache.dir";
which then would be ' /tmp/accumulo-vfs-cache-accumulo', but it seems this dir does not not need to exist and will be created. Could there be any other reason this would pop up? Can these settings be overridden somewhere?
java.lang.ClassNotFoundException: IO Error loading class org.apache.accumulo.tserver.compaction.DefaultCompactionStrategy
Do you have your accumulo jars in VFS? I would recommend against that, put them in ACCUMULO_HOME/lib. Those should not be reloaded between restarts and makes a lot of extra calls against HDFS than are necessary.
On Thu, Sep 27, 2018 at 2:36 PM Rob Verkuylen <[hidden email]> wrote:
Nothing in VFS except my jar file.
On Thu, Sep 27, 2018 at 8:50 PM Michael Wall <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|