You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by GitBox <gi...@apache.org> on 2020/01/02 19:03:36 UTC
[GitHub] [hbase] bharathv commented on issue #904: HBASE-23304: RPCs needed
for client meta information lookup
bharathv commented on issue #904: HBASE-23304: RPCs needed for client meta information lookup
URL: https://github.com/apache/hbase/pull/904#issuecomment-570307916
> 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.
I'm a little confused. With patches like #812 #830 etc all the running masters (active/stand-by) can serve the information needed by a connection registry. For example: stand-by masters keep track of active masters so that they can serve the "get active master" request. Client does not need to keep retrying until it finds an active master. On top of that we now also have the ability to hedge requests across masters (#954). Did I miss something?
----------------------------------------------------------------
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