[
https://issues.apache.org/jira/browse/KUDU-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010704#comment-18010704
]
Zoltan Martonka commented on KUDU-1973:
---------------------------------------
[https://gerrit.cloudera.org/#/c/22867/]
> Coalesce RPCs destined for the same server
> ------------------------------------------
>
> Key: KUDU-1973
> URL: https://issues.apache.org/jira/browse/KUDU-1973
> Project: Kudu
> Issue Type: Sub-task
> Components: rpc, tserver
> Affects Versions: 1.4.0
> Reporter: Adar Dembo
> Assignee: Ashwani Raina
> Priority: Major
> Labels: data-scalability
>
> The krpc subsystem ensures that only one _connection_ exists between any pair
> of nodes, but it doesn't coalesce the _RPCs_ themselves. In clusters with
> dense nodes (especially with a lot of tablets), there's often a great number
> of RPCs sent between pairs of nodes.
> We should explore ways of coalescing those RPCs. I don't know whether that
> would happen within the krpc system itself (i.e. in a payload-agnostic way),
> or whether we'd only coalesce RPCs known to be "hot" (like UpdateConsensus).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
