[
https://issues.apache.org/jira/browse/HBASE-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106897#comment-13106897
]
Gary Helmling commented on HBASE-4425:
--------------------------------------
Whoops, yes, let me update.
> Provide access to RpcServer instance from RegionServerServices
> --------------------------------------------------------------
>
> Key: HBASE-4425
> URL: https://issues.apache.org/jira/browse/HBASE-4425
> Project: HBase
> Issue Type: Improvement
> Components: coprocessors, regionserver
> Reporter: Gary Helmling
> Attachments: HBASE-4425.patch
>
>
> In some cases, RegionObserver coprocessors may want to directly access the
> running RpcServer instance on the region server. For token based
> authentication, for example, this is needed for a coprocessor to interact
> with the SecretManager that validates authentication tokens in the secure RPC
> engine. With the addition of async call handling on the server-side, this
> becomes additionally important if coprocessors want to send back delayed
> responses to clients. In this case, the coprocessor would need to be able to
> call RpcServer.getCurrentCall() to send back the response.
> So I propose we add access to the RpcServer in RegionServerServices:
> {code}
> /**
> * Returns a reference to the region server's RPC server
> */
> public RpcServer getRpcServer();
> {code}
> We can simultaneously drop the existing RegionServerServices.getRpcMetrics()
> method, since this could then be accessed via RpcServer.getRpcMetrics().
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
