is limiting
here.
Thomas
From: Reid Pinchback
Sent: Dienstag, 22. Oktober 2019 19:31
To: user@cassandra.apache.org
Subject: Re: Cassandra 2.1.18 - Question on stream/bootstrap throughput
Thanks for the reading Jon.
From: Jon Haddad mailto:j...@jonhaddad.com>>
Reply-To: "user@cassandra
Thanks for the reading Jon.
From: Jon Haddad
Reply-To: "user@cassandra.apache.org"
Date: Tuesday, October 22, 2019 at 12:32 PM
To: "user@cassandra.apache.org"
Subject: Re: Cassandra 2.1.18 - Question on stream/bootstrap throughput
Message from External Sender
C
ompacting received SSTables.
>
>
>
> We really see no resource (CPU, NW and disk) being somehow maxed out on
> any node, which would explain the limit in the area of the new node
> receiving data at ~ 180-200 Mbit/s.
>
>
>
> Thanks again,
>
> Thomas
>
>
>
>
e receiving data
at ~ 180-200 Mbit/s.
Thanks again,
Thomas
From: Oleksandr Shulgin
Sent: Dienstag, 22. Oktober 2019 16:35
To: User
Subject: Re: Cassandra 2.1.18 - Question on stream/bootstrap throughput
On Tue, Oct 22, 2019 at 12:47 PM Steinmaurer, Thomas
mailto:thomas.steinmau...@dynatrace
: Oleksandr Shulgin
Sent: Dienstag, 22. Oktober 2019 16:35
To: User
Subject: Re: Cassandra 2.1.18 - Question on stream/bootstrap throughput
On Tue, Oct 22, 2019 at 12:47 PM Steinmaurer, Thomas
mailto:thomas.steinmau...@dynatrace.com>>
wrote:
using 2.1.8, 3 nodes (m4.10xlarge, ESB SSD-based),
On Tue, Oct 22, 2019 at 12:47 PM Steinmaurer, Thomas <
thomas.steinmau...@dynatrace.com> wrote:
>
>
> using 2.1.8, 3 nodes (m4.10xlarge, ESB SSD-based), vnodes=256, RF=3, we
> are trying to add a 4th node.
>
>
>
> The two options to my knowledge, mainly affecting throughput, namely
> stream
A high level of compaction seems highly likely to throttle you by sending the
service into a GC death spiral, doubly-so if any repairs happen to be underway
at the same time (I may or may not have killed a few nodes this way, but I
admit nothing!). Even if not in GC hell, it can cause you to
