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

Duo Zhang commented on HBASE-16835:
-----------------------------------

{quote}
 Could we add the web ui port and other vitals to the master znode data. It is 
pb so extensible.
{quote}
They have already been in the same pb message. getMasterAddress and 
getMasterInfoPort actually get the same node from zk but retrieve the different 
part of the data. Maybe we need a new data structure?

{quote}
The latter will change later when we can split meta table but it is fine for 
now.
{quote}
Yeah but I think we still need to fetch the root region location from zk :)

{quote}
You think then that we'd have a new Registry API for async use? Could the new 
API underpin the old API?
{quote}
As we will build the old sync API on top of the new async API, I think we'd 
better not change the old code too much as it will finally be removed? And for 
this case, I want to move all zk related into ClusterRegistry. The old registry 
does not have the master address stuff. It is the MasterAddressTracker.

Thanks.

> Revisit the zookeeper usage at client side
> ------------------------------------------
>
>                 Key: HBASE-16835
>                 URL: https://issues.apache.org/jira/browse/HBASE-16835
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Duo Zhang
>
> Watcher or not.
> Curator or not.
> Keep connection or not.
> ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to