bharathv commented on a change in pull request #904: HBASE-23304: RPCs needed
for client meta information lookup
URL: https://github.com/apache/hbase/pull/904#discussion_r356363305
##########
File path: hbase-protocol-shaded/src/main/protobuf/Master.proto
##########
@@ -1200,3 +1200,47 @@ service HbckService {
rpc FixMeta(FixMetaRequest)
returns(FixMetaResponse);
}
+
+/** Request and response to get the clusterID for this cluster */
+message GetClusterIdRequest {
+}
+message GetClusterIdResponse {
+ /** Not set if cluster ID could not be determined. */
+ optional string cluster_id = 1;
+}
+
+/** Request and response to get the currently active master name for this
cluster */
+message GetActiveMasterRequest {
+}
+message GetActiveMasterResponse {
+ /** Not set if an active master could not be determined. */
+ optional ServerName server_name = 1;
+}
+
+/** Request and response to get the current list of meta region locations */
+message GetMetaRegionLocationsRequest {
+}
+message GetMetaRegionLocationsResponse {
+ /** Not set if meta region locations could not be determined. */
+ repeated RegionLocation meta_locations = 1;
+}
+
+/**
+ * Implements all the RPCs needed by clients to look up cluster meta
information needed for connection establishment.
+ */
+service ClientMetaService {
Review comment:
It just seemed logical to me to group these (and possibly related RPCs that
we add in the future) into a separate service that master is just implementing
today. Theoretically they are not tied to masters in any way. Any other process
can implement it too (like you already mentioned in the jira comments of
HBASE-18095). What do you think?
----------------------------------------------------------------
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:
us...@infra.apache.org
With regards,
Apache Git Services
