Hi Pubudu, Please stop adding dev@ back to this email's recipient list; this isn't an issue for HBase developers to address. Looking at what you've posted from hbase-site.xml, I recommend you start with the HBase Ref Guide, specifically section 2.4 on Fully Distributed setups [1]. I'd also recommend trying to use hostnames instead of IP addresses in your configurations, if possible; I've had issues in the past with DNS when providing HBase with IP addresses instead of FQDNs.
[1] http://hbase.apache.org/book.html#quickstart_fully_distributed -Dima On Sat, Jul 18, 2015 at 6:33 AM, Pubudu Gunatilaka <pubudu...@gmail.com> wrote: > Hi, > > I looked into HBASE-12954. But could not figure out a way of solving the > issue. I noticed one thing in region servers. When I try to add a region > server separately, it adds as two servers. One from the ip address and > other from the hostname. Is this an expected outcome? I have attached a > screen shot. > > Following are the configurations of my hbase-site.xml. > > <configuration> > <property> > <name>hbase.rootdir</name> > <value>hdfs://172.17.0.205:54310/hbase</value> > </property> > > <property> > <name>hbase.cluster.distributed</name> > <value>true</value> > </property> > > <property> > <name>hbase.zookeeper.property.dataDir</name> > <value>/opt/HBASE/zookeeper</value> > </property> > > <property> > <name>hbase.zookeeper.quorum</name> > <value>172.17.0.207</value> > </property> > > <property> > <name>hbase.master.info.bindAddress</name> > <value>172.17.0.216</value> > </property> > > <property> > <name>hbase.zookeeper.property.clientPort</name> > <value>2181</value> > </property> > > </configuration> > > Any help on this is appreciated. > > Thank you! > > > > On Sat, Jul 18, 2015 at 12:20 AM, Dima Spivak <dspi...@cloudera.com> > wrote: > >> +user@, dev@ to bcc >> >> Pubudu, >> >> I think you'll get more help on an issue like this on the users list. >> >> -Dima >> >> ---------- Forwarded message ---------- >> From: Ted Yu <yuzhih...@gmail.com> >> Date: Fri, Jul 17, 2015 at 5:40 AM >> Subject: Re: Hbase Fully distribution mode - Cannot resolve regionserver >> hostname >> To: "d...@hbase.apache.org" <d...@hbase.apache.org> >> >> >> Have you looked at >> HBASE-12954 Ability impaired using HBase on multihomed hosts >> >> Cheers >> >> On Fri, Jul 17, 2015 at 3:32 AM, Pubudu Gunatilaka <pubudu...@gmail.com> >> wrote: >> >> > Hi Devs, >> > >> > I am trying to run Hbase in fully distributed mode. So first I started >> > master node. Then I started regionserver. But I am getting following >> error. >> > >> > 2015-07-17 05:12:02,260 WARN [pod-35:16020.activeMasterManager] >> > master.AssignmentManager: Failed assignment of hbase:meta,,1.1588230740 >> to >> > pod-36,16020,1437109916288, trying to assign elsewhere instead; try=1 of >> 10 >> > java.net.UnknownHostException: unknown host: pod-36 >> > at >> > >> > >> >> org.apache.hadoop.hbase.ipc.RpcClientImpl$Connection.<init>(RpcClientImpl.java:296) >> > at >> > >> > >> >> org.apache.hadoop.hbase.ipc.RpcClientImpl.createConnection(RpcClientImpl.java:129) >> > at >> > >> > >> >> org.apache.hadoop.hbase.ipc.RpcClientImpl.getConnection(RpcClientImpl.java:1278) >> > at >> org.apache.hadoop.hbase.ipc.RpcClientImpl.call(RpcClientImpl.java:1152) >> > at >> > >> > >> >> org.apache.hadoop.hbase.ipc.AbstractRpcClient.callBlockingMethod(AbstractRpcClient.java:216) >> > at >> > >> > >> >> org.apache.hadoop.hbase.ipc.AbstractRpcClient$BlockingRpcChannelImplementation.callBlockingMethod(AbstractRpcClient.java:300) >> > at >> > >> > >> >> org.apache.hadoop.hbase.protobuf.generated.AdminProtos$AdminService$BlockingStub.openRegion(AdminProtos.java:21711) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.ServerManager.sendRegionOpen(ServerManager.java:712) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:2101) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1567) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.AssignmentManager.assign(AssignmentManager.java:1545) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.AssignmentManager.assignMeta(AssignmentManager.java:2630) >> > at org.apache.hadoop.hbase.master.HMaster.assignMeta(HMaster.java:820) >> > at >> > >> > >> >> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(HMaster.java:685) >> > at org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:165) >> > at org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1428) >> > at java.lang.Thread.run(Thread.java:745) >> > >> > >> > This error occurs as the master node cannot resolve the hostname of the >> > regionserver. According to the requirement of mine, I want to automate >> the >> > hbase installation with 1 master node and 4 regionservers. But at the >> > moment I don't have any possibility of updating master's /etc/hosts >> file. >> > From the hbase configuration side, will I be able to solve the problem? >> > >> > If the hbase can communicate with IP addresses or use the hostname, >> which >> > is already sent by regionserver to the master without updating >> /etc/hosts >> > file this issue can be solved. Similar approach can be found in hadoop >> as >> > well. Once the datanode connects to the namenode, it can communicate >> with >> > the datanode without updating /etc/hosts file. >> > >> > Any help on this is appreciated. >> > >> > Thank you! >> > >> > -- >> > >> > *Pubudu Gunatilaka* >> > >> > > > > -- > > *Pubudu Gunatilaka* > >
