cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9766) Bootstrap outgoing streaming speeds are much slower than during repair
Date Tue, 16 Feb 2016 21:28:18 GMT

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

Eric Evans commented on CASSANDRA-9766:
---------------------------------------

So if I'm understanding this correctly (and I'm probably not), increasing the receiving buffer
would get more of the data over the wire before blocking on the read from buffer, decompression,
etc (up to however much the buffer was increased by).  Is that right?  If so, that wouldn't
really help much; That would seem to imply that processing the compressed data is the bottleneck,
and that the blocking is (rightfully) applying back-pressure to the network-side.

> Bootstrap outgoing streaming speeds are much slower than during repair
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-9766
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9766
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Cassandra 2.1.2. more details in the pdf attached 
>            Reporter: Alexei K
>             Fix For: 2.1.x
>
>         Attachments: problem.pdf
>
>
> I have a cluster in Amazon cloud , its described in detail in the attachment. What I've
noticed is that we during bootstrap we never go above 12MB/sec transmission speeds and also
those speeds flat line almost like we're hitting some sort of a limit ( this remains true
for other tests that I've ran) however during the repair we see much higher,variable sending
rates. I've provided network charts in the attachment as well . Is there an explanation for
this? Is something wrong with my configuration, or is it a possible bug?



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

Mime
View raw message