After HBASE-10569, HMaster embeds a regionserver process that hosts system tables and that could be using this port (It will show up as HMaster pid if you check the process using this port). So you needn't explicitly start a regionserver in a single node installation.
On Wed, Nov 26, 2014 at 7:27 AM, guxiaobo1982 <[email protected]> wrote: > Hi, > > > I tried to install a single node hbase 0.99.1 with hadoop 2.5.2, but > failed with regionserver says: > > > > 2014-11-26 09:05:42,594 INFO [main] util.ServerCommandLine: > vmInputArguments=[-Dproc_regionserver, -XX:OnOutOfMemoryError=kill -9 %p, > -XX:+UseConcMarkSweepGC, -Dhbase.log.dir=/opt/hbase-0.99.1/ > > bin/../logs, -Dhbase.log.file=hbase-xiaobogu-regionserver-lix3.bh.com.log, > -Dhbase.home.dir=/opt/hbase-0.99.1/bin/.., -Dhbase.id.str=xiaobogu, > -Dhbase.root.logger=INFO,RFA, -Dhbase.security.logg > > er=INFO,RFAS] > > 2014-11-26 09:05:42,956 INFO [main] regionserver.RSRpcServices: > regionserver/lix3.bh.com/192.168.100.5:16020 server-side HConnection > retries=350 > > 2014-11-26 09:05:43,240 INFO [main] ipc.SimpleRpcScheduler: Using > deadline as user call queue, count=3 > > 2014-11-26 09:05:43,252 ERROR [main] > regionserver.HRegionServerCommandLine: Region server exiting > > java.lang.RuntimeException: Failed construction of Regionserver: class > org.apache.hadoop.hbase.regionserver.HRegionServer > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.constructRegionServer(HRegionServer.java:2443) > > at > org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.start(HRegionServerCommandLine.java:64) > > at > org.apache.hadoop.hbase.regionserver.HRegionServerCommandLine.run(HRegionServerCommandLine.java:87) > > at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:70) > > at > org.apache.hadoop.hbase.util.ServerCommandLine.doMain(ServerCommandLine.java:126) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.main(HRegionServer.java:2458) > > Caused by: java.lang.reflect.InvocationTargetException > > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native > Method) > > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) > > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > > at java.lang.reflect.Constructor.newInstance(Constructor.java:526) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.constructRegionServer(HRegionServer.java:2441) > > ... 5 more > > Caused by: java.net.BindException: Problem binding to > lix3.bh.com/192.168.100.5:16020 : 地址已在使用 > > at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2356) > > at > org.apache.hadoop.hbase.ipc.RpcServer$Listener.<init>(RpcServer.java:524) > > at > org.apache.hadoop.hbase.ipc.RpcServer.<init>(RpcServer.java:1884) > > at > org.apache.hadoop.hbase.regionserver.RSRpcServices.<init>(RSRpcServices.java:775) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.createRpcServices(HRegionServer.java:558) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.<init>(HRegionServer.java:477) > > ... 10 more > > Caused by: java.net.BindException: 地址已在使用 > > at sun.nio.ch.Net.bind0(Native Method) > > at sun.nio.ch.Net.bind(Net.java:444) > > at sun.nio.ch.Net.bind(Net.java:436) > > at > sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214) > > at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) > > at org.apache.hadoop.hbase.ipc.RpcServer.bind(RpcServer.java:2354) > > ... 15 more > > [xiaobogu@lix3 hbase-0.99.1]$ > > > > > It seems the 10620 port has already used by other processes, is there any > change with the default port number configurations for hadoop and hbase > with these new version? > > > > > Regards, -- Bharath Vissapragada <http://www.cloudera.com>
