[ 
https://issues.apache.org/jira/browse/HBASE-11467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mikhail Antonov updated HBASE-11467:
------------------------------------

    Description: 
Currently there' only one implementation of Registry interface, which is using 
ZK to get info about meta. Need to create implementation which will be using  
RPC calls to master the client is connected to.

That includes adding several new methods to master RPC protocol:

- GetMetaRegionLocation
- IsTableOnlineState
- GetCurrentNrHRS

Additionally, new HTTP endpoint would be added to the master, so anyone can 
request ClusterId without any authentication.

  was:
Currently there' only one implementation of Registry interface, which is using 
ZK to get info about meta. Need to create implementation which will be using  
RPC calls to master the client is connected to.

That includes adding several new methods to master RPC protocol:

- GetMetaRegionLocation
- GetClusterId
- IsTableOnlineState
- GetCurrentNrHRS 


> New impl of Registry interface not using ZK + new RPCs on master protocol
> -------------------------------------------------------------------------
>
>                 Key: HBASE-11467
>                 URL: https://issues.apache.org/jira/browse/HBASE-11467
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client, Consensus, Zookeeper
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>             Fix For: 2.0.0
>
>
> Currently there' only one implementation of Registry interface, which is 
> using ZK to get info about meta. Need to create implementation which will be 
> using  RPC calls to master the client is connected to.
> That includes adding several new methods to master RPC protocol:
> - GetMetaRegionLocation
> - IsTableOnlineState
> - GetCurrentNrHRS
> Additionally, new HTTP endpoint would be added to the master, so anyone can 
> request ClusterId without any authentication.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to