Thanks for trying out 0.80.0 release. The error you saw was due to hbase.tmp.dir pointing to path which was valid on the node where container was running but invalid on the client. In the retrieved hbase-site.xml, you can replace with the following:
<property><name>hbase.tmp.dir</name><value>/tmp/hbase-tmp</value><source/></property> This step is done automatically by hbase shell wrapper - see the last section of: http://slider.incubator.apache.org/docs/troubleshooting.html Cheers On Sun, May 10, 2015 at 9:29 PM, Rajesh Kartha <karth...@gmail.com> wrote: > Hello, > > I was trying the Slider 0.80 build (with HBase 0.98.8) in my YARN cluster > and which *does not* have security enabled, which means yarn-site.xml > has the following setting: > > <property> > <name>yarn.nodemanager.container-executor.class</name> > > <value>org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor</value> > </property> > > As a result the *containers *will be executed under the user '*yarn*' and > not as the user starting the application via Slider. > > I am able to start/stop the HBase cluster via Slider and even create tables > under the '*yarn*' user. > > However, when I switch to *another user* and use the HBase shell by passing > the hbase-site.xml (extracted via slider), I am not able to > create not query existing tables, the error I see is: > > ERROR: Failed to create local dir > > /hadoop/yarn/local/usercache/bigdata/appcache/application_1431039978132_0005/container_1431039978132_0005_01_000003/work/app/tmp/local/jars, > DynamicClassLoader failed to init > > I expected it to work seamlessly, hence wondering if I missed anything or > if this is the expected behavior. Any workarounds to get around this. > > Regards, > Rajesh >
