[
https://issues.apache.org/jira/browse/CASSANDRA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13165803#comment-13165803
]
Jonathan Ellis commented on CASSANDRA-3590:
-------------------------------------------
Not sure about this one:
1. Adding another TCP stream shouldn't give you more throughput or lower
latency unless you're cpu bound on the thread copying bytes out the first one,
which seems unlikely. (Or unless your second connection is actually over a
separate interface, which seems even less likely.)
2. We drop connections when the other end dies, so clearing out the messages
pending is the right thing to do. (Although here we may have FD false
positives, as in CASSANDRA-3569. But if so the fix is probably along the lines
Peter outlines there.)
> 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.1
>
>
> 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
