Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Once we have all the RPCs in place (via HBASE-23304), implement a pluggable master based AsyncRegistry (like ZKAsyncRegistry) which clients can use to directly connect to master and fetch all the meta information needed.
Attachments
Issue Links
- blocks
-
HBASE-23647 Make MasterRegistry the default registry impl
- Resolved
- is a parent of
-
PHOENIX-6523 Support for HBase Registry Implementations through Phoenix connection URL
- Resolved
- is blocked by
-
HBASE-23304 Implement RPCs needed for master based registry
- Resolved
-
HBASE-23259 Ability to run mini cluster using pre-determined available random ports
- Resolved
-
HBASE-23575 Remove dead code from AsyncRegistry interface
- Resolved
- is related to
-
HBASE-24265 Remove hedged rpc call support, implement the logic in MaterRegistry directly
- Resolved
-
HBASE-23648 Re-use underlying connection registry in RawAsyncHBaseAdmin
- Resolved
-
HBASE-23649 Implement an adaptive hedging policy
- Open
- relates to
-
HBASE-23604 Clarify AsyncRegistry usage in the code
- Resolved
- links to