[
https://issues.apache.org/jira/browse/CASSANDRA-3017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14133863#comment-14133863
]
Benedict commented on CASSANDRA-3017:
-------------------------------------
This is definitely a good idea. At the same time I think it might be worth
considering introducing an upper limit on either the total size of requests
we've currently got in-flight for MessagingService, or the total number, or
possibly both. Once the threshold is exceeded we stop consuming input from all
IncomingTcpConnection(s). This is not dramatically different to our imposition
of a max rpc count, but stops a single server being overloaded through a
hotspot of queries driven by non-token aware clients (but also from only a
slight variant on the malicious oversized payload attack).
> 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
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
