[ 
https://issues.apache.org/jira/browse/CASSANDRA-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

C. Scott Andreas updated CASSANDRA-13055:
-----------------------------------------
    Component/s: Repair

> DoS by StreamReceiveTask, during incremental repair
> ---------------------------------------------------
>
>                 Key: CASSANDRA-13055
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13055
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Repair
>            Reporter: Tom van der Woerdt
>            Priority: Major
>         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
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to