cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13055) DoS by StreamReceiveTask, during incremental repair
Date Tue, 20 Dec 2016 21:21:58 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765277#comment-15765277
] 

Paulo Motta commented on CASSANDRA-13055:
-----------------------------------------

bq. 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.

The changelog is inded wrong, but I actually I got confused and thought this was fixed on
CASSANDRA-12901 but I just checked and in fact wasn't so I updated the suggestion above.

> 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)

Mime
View raw message