[ https://issues.apache.org/jira/browse/CASSANDRA-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom van der Woerdt updated CASSANDRA-13055: ------------------------------------------- Reproduced In: 3.0.10 > 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 > > 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)