You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2017/09/21 04:30:00 UTC

[jira] [Commented] (HBASE-11466) HConnectionImplementation should not use ZK

    [ https://issues.apache.org/jira/browse/HBASE-11466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16174257#comment-16174257 ] 

stack commented on HBASE-11466:
-------------------------------

Kicking this out. We should do it but it is not being worked on for 2.0.

> 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, Consensus
>    Affects Versions: 2.0.0
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>            Priority: Critical
>
> 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.4.14#64029)