On Mon, Apr 29, 2013 at 3:52 PM, John Watson wrote:
> Same behavior on 1.1.3, 1.1.5 and 1.1.9.
> Currently: 1.2.3
(below snippets are from trunk)
./src/java/org/apache/cassandra/tools/NodeCmd.java
"
case SETCOMPACTIONTHROUGHPUT :
if (arguments.length != 1) { badUs
Same behavior on 1.1.3, 1.1.5 and 1.1.9.
Currently: 1.2.3
On Mon, Apr 29, 2013 at 11:43 AM, Robert Coli wrote:
> On Sun, Apr 28, 2013 at 2:28 PM, John Watson wrote:
> > Running these 2 commands are noop IO wise:
> > nodetool setcompactionthroughput 0
> > nodetool setstreamtrhoughput 0
>
>
On Sun, Apr 28, 2013 at 2:28 PM, John Watson wrote:
> Running these 2 commands are noop IO wise:
> nodetool setcompactionthroughput 0
> nodetool setstreamtrhoughput 0
What version of cassandra?
=Rob
The help command says 0 to disable:
setcompactionthroughput - Set the MB/s throughput cap for
compaction in the system, or 0 to disable throttling.
setstreamthroughput - Set the MB/s throughput cap for
streaming in the system, or 0 to disable throttling.
I also set both to 1000 and it also
Out of curiosity. Why did you decide to set it to 0 rather then 9. Does
any documentation anywhere say that setting to 0 disables the feature? I
have set streamthroughput higher and seen node join improvements. The
features do work however they are probably not your limiting factor.
Remember fo
Running these 2 commands are noop IO wise:
nodetool setcompactionthroughput 0
nodetool setstreamtrhoughput 0
If trying to recover or rebuild nodes, it would be super helpful to get
more than ~120mbit/s of streaming throughput (per session or ~500mbit
total) and ~5% IO utilization in (8) 15k di
