Return-Path: <user-return-53069-archive-asf-public=cust-asf.ponee.io@hbase.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 6C136200BFF
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 17 Jan 2017 16:48:03 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 6A815160B46; Tue, 17 Jan 2017 15:48:03 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 8E97E160B43
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 17 Jan 2017 16:48:02 +0100 (CET)
Received: (qmail 90252 invoked by uid 500); 17 Jan 2017 15:48:01 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 90235 invoked by uid 99); 17 Jan 2017 15:48:00 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jan 2017 15:48:00 +0000
Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 43BDC1A0440
	for <user@hbase.apache.org>; Tue, 17 Jan 2017 15:48:00 +0000 (UTC)
Received: by mail-wm0-f50.google.com with SMTP id c85so205662390wmi.1
        for <user@hbase.apache.org>; Tue, 17 Jan 2017 07:48:00 -0800 (PST)
X-Gm-Message-State: AIkVDXLoSTyk6jsLWCK9Ocu5lcSDp8Yp0szI2AGt26vnhBHY6F4mgzSaV63uBj9z+Zfs5IGKnqd14R8xLi+DrQ==
X-Received: by 10.223.173.43 with SMTP id p40mr27904615wrc.163.1484668078876;
 Tue, 17 Jan 2017 07:47:58 -0800 (PST)
MIME-Version: 1.0
References: <HK2PR02MB1058500CF07B0C03760B11DAA37D0@HK2PR02MB1058.apcprd02.prod.outlook.com>
 <CAKYcnAu2bcvJcYH26-gXtCNDcQHCcsUb6+Bp5i5yQeBZ1j=0GA@mail.gmail.com> <HK2PR02MB10581EF0B8FA720AB0DDED7FA37C0@HK2PR02MB1058.apcprd02.prod.outlook.com>
In-Reply-To: <HK2PR02MB10581EF0B8FA720AB0DDED7FA37C0@HK2PR02MB1058.apcprd02.prod.outlook.com>
From: Dima Spivak <dimaspivak@apache.org>
Date: Tue, 17 Jan 2017 15:47:48 +0000
X-Gmail-Original-Message-ID: <CAKYcnAvmnF43s+_LtecmZZZb8fmM2ju0SpyFqiG4t24Hxy26Fw@mail.gmail.com>
Message-ID: <CAKYcnAvmnF43s+_LtecmZZZb8fmM2ju0SpyFqiG4t24Hxy26Fw@mail.gmail.com>
Subject: Re: hbase has problems with two hostname
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f403045cf66073a67205464c39bb
archived-at: Tue, 17 Jan 2017 15:48:03 -0000

--f403045cf66073a67205464c39bb
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Is there any other DNS server running that might be confusing reverse
lookup? What happens if you run `host YOUR_RS_IP_ADDRESS`?

And what kind of machines are you using in your deployment?

Cheers,

On Mon, Jan 16, 2017 at 11:34 PM C R <cuirong198610@hotmail.com> wrote:

> Thanks,
>
>
>
>
>
> I deployed my HBase very simply, which has one Master and three
> regionservers.
>
>
>
>
>
> [hbase@bjsh19-16-30 conf]$ more regionservers
>
> bjsh19-16-33.qbos.com
>
> bjsh19-16-34.qbos.com
>
> bjsh19-16-35.qbos.com
>
> [hbase@bjsh19-16-30 conf]$ more hbase-site.xml
>
>
>
> ...
>
>
>
> <configuration>
>
> <property>
>
>         <name>zookeeper.znode.parent</name>
>
>                 <value>/hbase117</value>
>
>                 </property>
>
> <property>
>
>   <name>hbase.rootdir</name>
>
>         <value>hdfs://bidc/hbase117</value>
>
>                   </property>
>
> <property>
>
>   <name>hbase.zookeeper.quorum</name>
>
>         <value>bjsh19-16-30.qbos.com,bjsh19-16-31.qbos.com,
> bjsh19-16-32.qbos.com</value>
>
>                   </property>
>
> <property>
>
>   <name>hbase.cluster.distributed</name>
>
>         <value>true</value>
>
>                   </property>
>
> <property>
>
>   <name>hbase.zookeeper.property.clientPort</name>
>
>         <value>2181</value>
>
>                   </property>
>
> </configuration>
>
>
>
>
>
> The special place is the file /etc/hosts with one ip mapping to two
> hostnames on all nodes,so it will have the message:
>
>
>
> ...
>
>
>
> the server that tried to transition was wjsa-tsl05,16020,1484623636195 no=
t
> the expected bjsh19-16-34.qbos.com,16020,1484623636195
>
>
>
> ...
>
>
>
>
>
> ________________________________
>
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Dima Spivak <dimaspivak@apache.org>
>
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2017=E5=B9=B41=E6=9C=8817=E6=97=A5 =
4:50
>
> =E6=94=B6=E4=BB=B6=E4=BA=BA: user@hbase.apache.org
>
> =E4=B8=BB=E9=A2=98: Re: hbase has problems with two hostname
>
>
>
> Hi C R,
>
>
>
> Like many Hadoop-like services, HBase is pretty temperamental about
>
> requiring forward and reverse DNS to work properly. FWIW, the configurati=
on
>
> file where you can populate RegionServers doesn't tend to matter as long =
as
>
> the hbase-site.xml file is populated correctly (it's just used to start
>
> daemons from one place).
>
>
>
> If you pass along more details about how exactly you're deploying HBase, =
we
>
> might be able to give more advice.
>
>
>
> On Mon, Jan 16, 2017 at 8:00 PM C R <cuirong198610@hotmail.com> wrote:
>
>
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > more /etc/hosts
>
> >
>
> >
>
> > ...
>
> >
>
> >
>
> >
>
> >
>
> > 10.19.16.31  bjsh19-16-31.qbos.com    wjsa-tsl02
>
> >
>
> >
>
> > ...
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > There will have six regionservers listed in web console, but
>
> >
>
> > only three in the configuration file,  metadata tables also are not
> online
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > Hmaster will be dead after a while.
>
> >
>
> >
>
> > what should I do?
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > snapshot:
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > 2017-01-17 11:45:24,394 INFO
>
> >  [MASTER_SERVER_OPERATIONS-bjsh19-16-30:16000-0]
> master.AssignmentManager:
>
> > Assigning
> hbase:namespace,,1484623643279.30fab746cb3b6ceadcbda421459204b9.
>
> > to bjsh19-16-34.qbos.com,16020,1484623636195
>
> >
>
> >
>
> > 2017-01-17 11:45:24,395 INFO  [bjsh19-16-30:16000.activeMasterManager]
>
> > master.AssignmentManager: Joined the cluster in 23ms, failover=3Dtrue
>
> >
>
> >
>
> > 2017-01-17 11:50:24,314 FATAL [bjsh19-16-30:16000.activeMasterManager]
>
> > master.HMaster: Failed to become active master
>
> >
>
> >
>
> > java.io.IOException: Timedout 300000ms waiting for namespace table to b=
e
>
> > assigned
>
> >
>
> >
>
> >         at
>
> >
> org.apache.hadoop.hbase.master.TableNamespaceManager.start(TableNamespace=
Manager.java:104)
>
> >
>
> >
>
> >         at
>
> > org.apache.hadoop.hbase.master.HMaster.initNamespace(HMaster.java:986)
>
> >
>
> >
>
> >         at
>
> >
> org.apache.hadoop.hbase.master.HMaster.finishActiveMasterInitialization(H=
Master.java:780)
>
> >
>
> >
>
> >         at
>
> > org.apache.hadoop.hbase.master.HMaster.access$500(HMaster.java:183)
>
> >
>
> >
>
> >         at
> org.apache.hadoop.hbase.master.HMaster$1.run(HMaster.java:1652)
>
> >
>
> >
>
> >         at java.lang.Thread.run(Thread.java:745)
>
> >
>
> >
>
> > 2017-01-17 11:50:24,315 FATAL [bjsh19-16-30:16000.activeMasterManager]
>
> > master.HMaster: Master server abort: loaded coprocessors are: []
>
> >
>
> >
>
> > 2017-01-17 11:50:24,316 FATAL [bjsh19-16-30:16000.activeMasterManager]
>
> > master.HMaster: Unhandled exception. Starting shutdown.
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > ...
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> > 2017-01-17 11:27:17,926 INFO  [regionserver/
>
> > bjsh19-16-34.qbos.com/10.19.16.34:16020] regionserver.HRegionServer:
>
> > Serving as wjsa-tsl05,16020,1
>
> >
>
> >
>
> > 484623636195, RpcServer on bjsh19-16-34.qbos.com/10.19.16.34:16020,
>
> > sessionid=3D0x154563e43e30179
>
> >
>
> >
>
> > 2017-01-17 11:27:17,934 INFO  [regionserver/
>
> > bjsh19-16-34.qbos.com/10.19.16.34:16020]
> quotas.RegionServerQuotaManager:
>
> > Quota support disabled
>
> >
>
> >
>
> > 2017-01-17 11:27:23,966 INFO
>
> >  [PriorityRpcServer.handler=3D14,queue=3D0,port=3D16020]
>
> > regionserver.RSRpcServices: Open hbase:namespace,,148462364327
>
> >
>
> >
>
> > 9.30fab746cb3b6ceadcbda421459204b9.
>
> >
>
> >
>
> > 2017-01-17 11:27:24,008 WARN  [RS_OPEN_REGION-bjsh19-16-34:16020-0]
>
> > zookeeper.ZKAssign: regionserver:16020-0x154563e43e30179,
> quorum=3Dbjsh19-16
>
> >
>
> >
>
> > -30:2181,bjsh19-16-31:2181,bjsh19-16-32:2181, baseZNode=3D/hbase115new
>
> > Attempt to transition the unassigned node for 30fab746cb3b6ceadcbda4214=
59
>
> >
>
> >
>
> > 204b9 from M_ZK_REGION_OFFLINE to RS_ZK_REGION_OPENING failed, the serv=
er
>
> > that tried to transition was wjsa-tsl05,16020,1484623636195 not the
>
> >
>
> >
>
> > expected bjsh19-16-34.qbos.com,16020,1484623636195
>
> >
>
> >
>
> > 2017-01-17 11:27:24,008 WARN  [RS_OPEN_REGION-bjsh19-16-34:16020-0]
>
> > coordination.ZkOpenRegionCoordination: Failed transition from OFFLINE t=
o
> O
>
> >
>
> >
>
> > PENING for region=3D30fab746cb3b6ceadcbda421459204b9
>
> >
>
> >
>
> > 2017-01-17 11:27:24,008 WARN  [RS_OPEN_REGION-bjsh19-16-34:16020-0]
>
> > handler.OpenRegionHandler: Region was hijacked? Opening cancelled for
> enco
>
> >
>
> >
>
> > dedName=3D30fab746cb3b6ceadcbda421459204b9
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
>

--f403045cf66073a67205464c39bb--