cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giampaolo (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11516) Make max number of streams configurable
Date Thu, 16 Jun 2016 13:13:05 GMT

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

Giampaolo commented on CASSANDRA-11516:
---------------------------------------

I'm studying how to solve this issue. A quick question: do you mean to put a configuration
for [this line|https://github.com/apache/cassandra/blob/3dcbe90e02440e6ee534f643c7603d50ca08482b/src/java/org/apache/cassandra/streaming/StreamReceiveTask.java#L62]
using {{newFixedThreadPool}} and defaulting to {{FBUtilities#getAvailableProcessors}}?

> Make max number of streams configurable
> ---------------------------------------
>
>                 Key: CASSANDRA-11516
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11516
>             Project: Cassandra
>          Issue Type: New Feature
>            Reporter: Sebastian Estevez
>              Labels: lhf
>
> Today we default to num cores. In large boxes (many cores), this is suboptimal as it
can generate huge amounts of garbage that GC can't keep up with.
> Usually we tackle issues like this with the streaming throughput levers but in this case
the problem is CPU consumption by StreamReceiverTasks specifically in the IntervalTree build
-- https://github.com/apache/cassandra/blob/cassandra-2.1.12/src/java/org/apache/cassandra/utils/IntervalTree.java#L257
> We need a max number of parallel streams lever to hanlde this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message