Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 31 May 2017 11:40:04 +0000 (UTC)
From: "liubangchen (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13075120.1495788810000.330294.1496230804700@Atlassian.JIRA>
In-Reply-To: <JIRA.13075120.1495788810000@Atlassian.JIRA>
References: <JIRA.13075120.1495788810000@Atlassian.JIRA> <JIRA.13075120.1495788810391@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HBASE-18124) Make Hbase Communication Support
 Virtual Network
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 31 May 2017 11:40:08 -0000


     [ https://issues.apache.org/jira/browse/HBASE-18124?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

liubangchen updated HBASE-18124:
--------------------------------
    Status: Open  (was: Patch Available)

> Make Hbase Communication Support Virtual Network
> ------------------------------------------------
>
>                 Key: HBASE-18124
>                 URL: https://issues.apache.org/jira/browse/HBASE-18124
>             Project: HBase
>          Issue Type: New Feature
>          Components: Client, hbase, master
>            Reporter: liubangchen
>            Assignee: liubangchen
>         Attachments: 1.jpg, HBASE-18124.patch, HBASE-18124.pdf
>
>
> Hbase only have one way to locate hmaster or hregionserver not like hdfs =
has two way to locate datanode used by name or hostname.
> I'm a engineer of cloud computing , and I'm in charge of to make Hbase as=
 a cloud service.
> Our Hbase cloud service architecture shown as follows:  1.jpg
> 1.VM
>     User=E2=80=99s Hbase client work in vm and use virtual ip address to =
access hbase cluster.
> 2.NAT
>     Network Address Translation, vip(Virtual Network Address) to pip (Phy=
sical Network Address)
> 3. HbaseCluster Service
>      HbaseCluster Service work in physical network
> Problem
>      Vm use vip to communicate with hbase cluster, but hbase have only on=
e way to communicate with each server using host which is setting by parame=
ters hbase.regionserver.hostname or hbase.master.hostname. When HMaster sta=
rtup will publish master address and meta region server address  in zookeep=
er, then the address is pip(Physical Network Address) . Because hbase clust=
er work in physical network. But the problem is that when vm get  the addre=
ss from zookeeper is pip, not vip. If I set host as vip, it will has proble=
ms for hbase cluster communication inside. so it needs two ways for communi=
cation setting by parameters.
> Solution
>     1.   protocol extend=20
>       change strcut ServerName as
>       {code}
>           message ServerName {
>               required string host_name =3D 1;
>              optional uint32 port =3D 2;
>              optional uint64 start_code =3D 3;
>               optional string name=3D4;  //new field=20
>          }
>       {code}
>      It will be publish in zookeeper. We can choose host_name or name con=
figured by parameters hbase.client.use.hostname
> 2.   metatable extend=20
>        Add a column to hbase:meta named info:namelocation . So the origin=
al column info:server configured with hbase.regionserver.hostname, and the =
new column info:namelocation  configured with hbase.regionserver.servername
> 3.   hbase-server
>        When regionserver startup, configured  hbase.regionserver.hostname=
 as pip and configured hbase.regionserver.servername as vip. Then hbase.reg=
ionserver.hostname will be writed in ServerName's host_name, and hbase.regi=
onserver.servername will be writed in ServerName's name.When hmaster startu=
p, configured hbase.hmaster.hostname as pip and configured  hbase.hmaster.s=
ervername as vip. Then hbase.hmaster.hostname will be writed in ServerName'=
s host_name, and hbase.hmaster.servername will be writed in ServerName's na=
me.
> 4.   hbase-client
>       Add a parameters named hbase.client.use.hostname to use vip or pip.
> This patch is base on Hbase-1.3.0


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)