[
https://issues.apache.org/jira/browse/CASSANDRA-9237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517262#comment-14517262
]
Ariel Weisberg commented on CASSANDRA-9237:
-------------------------------------------
I was thinking the advantage of SCTP is that it wouldn't require an extra
thread since it looks like you can block a single thread on read and receive
messages for multiple streams. It's a tough cell because there is nothing drop
in about SCTP so it doesn't really solve the hard problem.
I don't actually see an issue with 3 sockets between nodes unless someone can
point out a downside other than a small amount of memory. Having more threads I
am not a fan of if only because of the stack scanning and noise in thread dumps.
Do we know for certain that having large and small messages go over separate
sockets actually makes life better? I went along with it on faith, but I am not
sure what that buys you on a LAN.
Could we do something simple and just use the 2nd socket for Gossip and call it
done?
> Gossip messages subject to head of line blocking by other intra-cluster
> traffic
> -------------------------------------------------------------------------------
>
> Key: CASSANDRA-9237
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9237
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ariel Weisberg
> Assignee: Ariel Weisberg
>
> Reported as an issue over less than perfect networks like VPNs between data
> centers.
> Gossip goes over the small message socket where small is 64k which isn't
> particularly small. This is done for performance to keep most traffic on one
> hot socket.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
