[
https://issues.apache.org/jira/browse/CASSANDRA-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765237#comment-15765237
]
Tom van der Woerdt edited comment on CASSANDRA-13055 at 12/20/16 9:06 PM:
--------------------------------------------------------------------------
https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt suggests
CASSANDRA-12901 was merged in 3.0.10, not 3.0.11. I'm afraid it's already
running :(
In case the changelog is wrong and it really is for 3.0.11: I'll have a look at
getting some build tools up, so I can actually run unreleased versions. May
take a while though.
was (Author: tvdw):
https://github.com/apache/cassandra/blob/cassandra-3.0/CHANGES.txt suggests
CASSANDRA-12901 was merged in 3.0.10, not 3.0.11. I'm afraid it's already
running :(
> DoS by StreamReceiveTask, during incremental repair
> ---------------------------------------------------
>
> Key: CASSANDRA-13055
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13055
> Project: Cassandra
> Issue Type: Bug
> Reporter: Tom van der Woerdt
> Attachments: untitled 2.txt
>
>
> There's no limit on how many StreamReceiveTask there can be, and during an
> incremental repair on a vnode cluster with high replication factors, this can
> lead to thousands of conccurent StreamReceiveTask threads, effectively DoSing
> the node.
> I just found one of my nodes with 1000+ loadavg, caused by 1363 concurrent
> StreamReceiveTask threads.
> That sucks :)
> I think :
> * Cassandra shouldn't allow more than X concurrent StreamReceiveTask threads
> * StreamReceiveTask threads should be at a lower priority, like compaction
> threads
> Alternative ideas welcome as well, of course.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
