You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Vijay (Commented) (JIRA)" <ji...@apache.org> on 2012/01/17 07:10:40 UTC
[jira] [Commented] (CASSANDRA-3590) Use multiple connection to
share the OutboutTCPConnection
[ https://issues.apache.org/jira/browse/CASSANDRA-3590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187471#comment-13187471 ]
Vijay commented on CASSANDRA-3590:
----------------------------------
My Conclusion of the test is, Multiple connections makes sense only while talking over Multiple DC's... Within a AWS Region/DC the latencies/Delays aren't that much and is not noticeable... but it definitely is noticeable in the Multi-DC setup.
> 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