You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Umesh Agashe (JIRA)" <ji...@apache.org> on 2016/09/12 19:05:21 UTC
[jira] [Created] (HBASE-16619) Following the quick start guide
fails to launch master due to SecureBulkLoadEndpoint
Umesh Agashe created HBASE-16619:
------------------------------------
Summary: Following the quick start guide fails to launch master due to SecureBulkLoadEndpoint
Key: HBASE-16619
URL: https://issues.apache.org/jira/browse/HBASE-16619
Project: HBase
Issue Type: Bug
Components: documentation, master
Affects Versions: 2.0.0
Reporter: Umesh Agashe
Assignee: Umesh Agashe
Priority: Critical
Followed the quick start guide for standalone hbase instance. HMaster instance doesn't start. Log file has following error:
{code}
2016-09-12 11:53:43,580 ERROR [main] regionserver.SecureBulkLoadManager: Failed to create or set permission on staging directory /user/uagashe/hbase-staging
ExitCodeException exitCode=1: chmod: /user/uagashe/hbase-staging: No such file or directory
at org.apache.hadoop.util.Shell.runCommand(Shell.java:545)
at org.apache.hadoop.util.Shell.run(Shell.java:456)
at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:722)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:815)
at org.apache.hadoop.util.Shell.execCommand(Shell.java:798)
at org.apache.hadoop.fs.RawLocalFileSystem.setPermission(RawLocalFileSystem.java:728)
at org.apache.hadoop.fs.FilterFileSystem.setPermission(FilterFileSystem.java:502)
at org.apache.hadoop.hbase.regionserver.SecureBulkLoadManager.start(SecureBulkLoadManager.java:124)
at org.apache.hadoop.hbase.regionserver.HRegionServer.<init>(HRegionServer.java:626)
at org.apache.hadoop.hbase.master.HMaster.<init>(HMaster.java:409)
at org.apache.hadoop.hbase.master.HMasterCommandLine$LocalHMaster.<init>(HMasterCommandLine.java:307)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.apache.hadoop.hbase.util.JVMClusterUtil.createMasterThread(JVMClusterUtil.java:140)
at org.apache.hadoop.hbase.LocalHBaseCluster.addMaster(LocalHBaseCluster.java:221)
at org.apache.hadoop.hbase.LocalHBaseCluster.<init>(LocalHBaseCluster.java:156)
at org.apache.hadoop.hbase.master.HMasterCommandLine.startMaster(HMasterCommandLine.java:226)
at org.apache.hadoop.hbase.master.HMasterCommandLine.run(HMasterCommandLine.java:139)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70)
at org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:127)
at org.apache.hadoop.hbase.master.HMaster.main(HMaster.java:2469)
2016-09-12 11:53:43,581 ERROR [main] master.HMasterCommandLine: Master exiting
{code}
Workaround for this is to add following config point to conf/hbase-site.xml:
{code}
<property>
<name>hbase.bulkload.staging.dir</name>
<value>file:///Users/uagashe/dev/apache/hbase-standalone/staging</value>
</property>
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)