[GitHub] [hbase] ndimiduk commented on issue #904: HBASE-23304: RPCs needed for client meta information lookup

[GitBox <gi...@apache.org>]

ndimiduk commented on issue #904: HBASE-23304: RPCs needed for client meta information lookup
URL: https://github.com/apache/hbase/pull/904#issuecomment-570300809
 
 
   > However, I'd like to see a larger design discussion on this API.
   
   I don't see this covered in the design doc at all. I was hoping to see some kind of state diagram that show the happy-path and error-case RPC calls made during client initialization, making use of these 3 new endpoints. Are there places where we can reduce the necessary RPCs? For example, how about a removing "get active master" and just have the client call "get meta locations". If the client happens to be communicating with the active master, it's saved an RPC. If it's not the active master, the failure response can contain the location of the active master. For reference, consider an HTTP 301 response.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services