[
https://issues.apache.org/jira/browse/CASSANDRA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187478#comment-13187478
]
Peter Schuller commented on CASSANDRA-3590:
-------------------------------------------
I just wanted to chime in and say that multiple TCP connections definitely do
make a difference on high-latency connections; this is empirically obvious
again and again when performing bulk transfers non-locally across the internet
and needing to up the concurrency to achieve throughput.
There are claims that TCP properly tuned will work properly with high latencies
over the internet, but all my practical experience still is that the easiest
way to get good throughput across arbitrary endpoints over the internet is just
just up the concurrency. Whether or not TCP theoretically works under feasibly
optimal circumstances is up for debate, but it seems to me that in practice
multiple connections is an easy solution which pretty much always works. It
should also translate well to a variety of operating system environments and
not require detailed kernel tuning/knowledge to make happen.
> Use multiple connection to share the OutboutTCPConnection
> ---------------------------------------------------------
>
> Key: CASSANDRA-3590
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3590
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1
> Reporter: Vijay
> Assignee: Vijay
> Priority: Minor
> Fix For: 1.2
>
> Attachments: TCPTest.xlsx, TCPTest.zip
>
>
> Currently there is one connection between any given host to another host in
> the cluster, the problem with this is:
> 1) This can become a bottleneck in some cases where the latencies are higher.
> 2) When a connection is dropped we also drop the queue and recreate a new one
> and hence the messages can be lost (Currently hints will take care of it and
> clients also can retry)
> by making it a configurable option to configure the number of connections and
> also making the queue common to those connections the above 2 issues can be
> resolved.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
