[
https://issues.apache.org/jira/browse/CASSANDRA-3378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Michalski updated CASSANDRA-3378:
----------------------------------------
Attachment: cassandra-3378-v2.patch
Thanks for reviewing, Brandon.
Changes in v2:
1) Remove receive buffer setting from OutboundTcpConnection - as it's being
used for Messaging purposes only and not really needed there
2) Set receive buffer (only) for IncommingTcpConnection. My concern is the way
of changing this parameter in a kind of "wide" way - not only for streaming
(for which it makes sense for me), but much earlier, so it "affects" messaging
parts of code too. I'm unsure of the impact it may have on the messaging
service in general - I don't have that much experience with Cassandra & network
programming to judge it "just like that".
> Allow configuration of storage protocol socket buffer
> -----------------------------------------------------
>
> Key: CASSANDRA-3378
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3378
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Brandon Williams
> Assignee: Michał Michalski
> Priority: Minor
> Labels: lhf
> Attachments: cassandra-3378-v1.patch, cassandra-3378-v2.patch
>
>
> Similar to rpc_[send,recv]_buff_size_in_bytes, we should expose this for high
> latency connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
