[
https://issues.apache.org/jira/browse/CASSANDRA-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495852#comment-13495852
]
Kirk True commented on CASSANDRA-3017:
--------------------------------------
I'd love to research the relationship between Thrift and intra-cluster
messages. Can you provide a sentence or two about exactly what that entails?
* Do I simply measure this via a series of get requests of varying column
slices and column data size, or does it need to be exhaustive for every message
type?
* Can the request sizes be gleaned with more logging or do I need to bust out
Wireshark?
* Is the data size for inter-node messages constant with respect to the initial
Thrift message or is some kind of compression in the mix?
> add a Message size limit
> ------------------------
>
> Key: CASSANDRA-3017
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3017
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Kirk True
> Priority: Minor
> Labels: lhf
> Attachments:
> 0001-use-the-thrift-max-message-size-for-inter-node-messa.patch,
> trunk-3017.txt
>
>
> We protect the server from allocating huge buffers for malformed message with
> the Thrift frame size (CASSANDRA-475). But we don't have similar protection
> for the inter-node Message objects.
> Adding this would be good to deal with malicious adversaries as well as a
> malfunctioning cluster participant.
--
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
