Hey Bryan,
I haven't change this setting, but it looks like this is the same
setting that can be changed with "nodetool setstreamthroughput"?
It sounds pretty interesting at a first glance, but FWIW, the limit was
12.6 MB/s, not 25 MB/s (so effectively 100 Mb/s).
On 12/03/2015 11:40 PM,
Thanks for your answer Rob,
On 12/03/2015 08:32 PM, Robert Coli wrote:
On Thu, Dec 3, 2015 at 7:51 AM, Jonathan Ballet > wrote:
I noticed it's not really fast and my monitoring system shows that
the traffic incoming on this node is exactly
If you change stream throughput it won't affect currently running streams
but it should affect new ones.
all the best,
Sebastián
On Dec 4, 2015 5:39 AM, "Jonathan Ballet" wrote:
> Thanks for your answer Rob,
>
> On 12/03/2015 08:32 PM, Robert Coli wrote:
>
>> On Thu, Dec 3,
Hi,
I added a new node to my cluster but in a new datacenter. After updating
the keyspace replication factor values (using the
NetworkTopologyStrategy strategy), I'm now running a "nodetool rebuild"
on the new node.
I noticed it's not really fast and my monitoring system shows that the
On Thu, Dec 3, 2015 at 7:51 AM, Jonathan Ballet wrote:
> I noticed it's not really fast and my monitoring system shows that the
> traffic incoming on this node is exactly at 100Mb/s (12.6MB/s). I know it
> can be much more than that (I just tested sending a file through SSH
>
Jonathan: Have you changed stream_throughput_outbound_megabits_per_sec in
cassandra.yaml?
# Throttles all outbound streaming file transfers on this node to the
# given total throughput in Mbps. This is necessary because Cassandra does
# mostly sequential IO when streaming data during bootstrap or