cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk True (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3017) add a Message size limit
Date Tue, 13 Nov 2012 02:03:12 GMT


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:
>             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,
> 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
> 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:

View raw message