[
https://issues.apache.org/jira/browse/HBASE-9461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-9461:
-------------------------
Attachment: ipc2.ucls
The ipc package has three different 'Context' classes going on:
+ Scheduler Context (Context base class is inner class of RpcScheduler but
RpcSchedulerContextImpl is inner class of RpcServer -- fun).
+ We have a RequestContext which is set by CallRunner on each invocation --
nothing to do w/ scheduler context
+ Calls have an RpcCallContext which is something that is different again.
> Some doc and cleanup in RPCServer
> ---------------------------------
>
> Key: HBASE-9461
> URL: https://issues.apache.org/jira/browse/HBASE-9461
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 9461.txt, ipc2.ucls
>
>
> RPC is a dog to follow. I want to do buffer pooling for reading requests but
> its tough drawing the diagram of who is doing what when. HBASE-8884 seems to
> have made it more involved still. This issue is about doing a bit of
> untangling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
