[
https://issues.apache.org/jira/browse/HBASE-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14946052#comment-14946052
]
stack commented on HBASE-14479:
-------------------------------
Here's link http://www.kircher-schwanninger.de/michael/publications/lf.pdf I
like the explanation here too:
http://stackoverflow.com/questions/3058272/explain-leader-follower-pattern
Patch seems good. You tried it [~ikeda] (if you'd messed up, unit tests would
be failing...) Anyway we could figure if a benefit? I can try running on a
cluster and see.... Thanks [~ikeda]
> Apply the Leader/Followers pattern to RpcServer's Reader
> --------------------------------------------------------
>
> Key: HBASE-14479
> URL: https://issues.apache.org/jira/browse/HBASE-14479
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC, Performance
> Reporter: Hiroshi Ikeda
> Assignee: Hiroshi Ikeda
> Priority: Minor
> Attachments: HBASE-14479-V2.patch, HBASE-14479-V2.patch,
> HBASE-14479.patch
>
>
> {{RpcServer}} uses multiple selectors to read data for load distribution, but
> the distribution is just done by round-robin. It is uncertain, especially for
> long run, whether load is equally divided and resources are used without
> being wasted.
> Moreover, multiple selectors may cause excessive context switches which give
> priority to low latency (while we just add the requests to queues), and it is
> possible to reduce throughput of the whole server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
