bharathv commented on a change in pull request #1890:
URL: https://github.com/apache/hbase/pull/1890#discussion_r439658505



##########
File path: src/main/asciidoc/_chapters/architecture.adoc
##########
@@ -271,18 +271,18 @@ This connection registry implementation is responsible 
for fetching the followin
 * Cluster ID (unique to this cluster)
 
 This information is needed as a part of various client operations like 
connection set up, scans,
-gets etc. Up until releases 2.x.y, the default connection registry is based on 
ZooKeeper as the
-source of truth and the the clients fetched the metadata from zookeeper 
znodes. As of release 3.0.0,
-the default implementation for connection registry has been switched  to a 
master based
-implementation. With this change, the clients now fetch the required metadata 
from master RPC end
-points directly. This change was done for the following reasons.
+gets, etc. Traditionally, the connection registry implementation has been 
based on ZooKeeper as the
+source of truth and clients fetched the metadata directly from the ZooKeeper 
quorum. HBase 2.3.0

Review comment:
       I didn't backport the patches yet. Will do it in the coming weeks. Will 
revisit this section once the backport is done.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to