[
https://issues.apache.org/jira/browse/CASSANDRA-8692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360966#comment-14360966
]
Tupshin Harper commented on CASSANDRA-8692:
-------------------------------------------
I commented on CASSANDRA-7032 that "It seems like there might be a way to
constrain vnode RDF (replication distribution factor) in the general scope of
this ticket as well."
I feel like there are some very compelling availability arguments (in addition
to these possible performance optimizations) in favor of being able to
constrain how many other nodes (within a DC) that a given vnode-enabled node
actually replicates with.
e.g. you could have 256 vnodes, but guarantee that those 256 would only
replicate to 32 (out of possibly thousands) of other nodes.
> Coalesce intra-cluster network messages
> ---------------------------------------
>
> Key: CASSANDRA-8692
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8692
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
> Fix For: 2.1.4
>
> Attachments: batching-benchmark.png
>
>
> While researching CASSANDRA-8457 we found that it is effective and can be
> done without introducing additional latency at low concurrency/throughput.
> The patch from that was used and found to be useful in a real life scenario
> so I propose we implement this in 2.1 in addition to 3.0.
> The change set is a single file and is small enough to be reviewable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
