hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Antonov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-11466) HConnectionImplementation should not use ZK
Date Mon, 07 Jul 2014 18:52:33 GMT

     [ https://issues.apache.org/jira/browse/HBASE-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mikhail Antonov updated HBASE-11466:
------------------------------------

    Description: 
Currently ConnectionManager.HConnectionImplementation uses ZK to get address of current master.
Should instead use pluggable interface to get location of master to connect to (current active
master in the cluster, until we have multiple active masters) elsewhere (e.g. round-robin
over the list of masters set in the client's hbase-site.xml).

Currently it uses MasterAddressTracker, which reads from ZK, and this is the only place where
MasterAddressTracker is used on the client side (except ZkUtil util method which dumps ZK
namespace to log). So implementation of  failover proxy which fails over multiple masters
will probably used only here.

  was:Currently ConnectionManager.HConnectionImplementation uses ZK to get address of current
master. Should instead use pluggable interface to get location of master to connect to (current
active master in the cluster, until we have multiple active masters) elsewhere (e.g. round-robin
over the list of masters set in the client's hbase-site.xml)


> HConnectionImplementation should not use ZK
> -------------------------------------------
>
>                 Key: HBASE-11466
>                 URL: https://issues.apache.org/jira/browse/HBASE-11466
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>    Affects Versions: 2.0.0
>            Reporter: Mikhail Antonov
>             Fix For: 2.0.0
>
>
> Currently ConnectionManager.HConnectionImplementation uses ZK to get address of current
master. Should instead use pluggable interface to get location of master to connect to (current
active master in the cluster, until we have multiple active masters) elsewhere (e.g. round-robin
over the list of masters set in the client's hbase-site.xml).
> Currently it uses MasterAddressTracker, which reads from ZK, and this is the only place
where MasterAddressTracker is used on the client side (except ZkUtil util method which dumps
ZK namespace to log). So implementation of  failover proxy which fails over multiple masters
will probably used only here.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message