thanks! I'll be watching this issue closely.
On Apr 9, 2011, at 5:41 AM, Chris Goffinet wrote:
> We also have a ticket open at
>
> https://issues.apache.org/jira/browse/CASSANDRA-2399
>
> We have observed in production the impact of streaming data to new nodes
> being added. We actually have
We also have a ticket open at
https://issues.apache.org/jira/browse/CASSANDRA-2399
We have observed in production the impact of streaming data to new nodes being
added. We actually have our entire dataset in page cache in one of our
clusters, our 99th percentiles go from 20ms to >1 second on s
My brain just started working. The streaming for the move may need to be
throttled, but once the file has been received the bloom filters, row indexes
and secondary indexes are built. That will also take some effort, do you have
any secondary indexes?
If you are doing a move again could you tr
thanks for the response Aaron. Our cluster has 6 nodes with 10 GB load on
each. RF=3.AMD 64 bit Blades, Quad Core, 8 GB ram, running Debian Linux.
Swap off. Cassandra 0.7.4
On Apr 6, 2011, at 2:40 AM, aaron morton wrote:
> Not that I know of, may be useful to be able to throttle thi
Not that I know of, may be useful to be able to throttle things. But if the
receiving node has little head room it may still be overwhelmed.
Currently there is a single thread for streaming. If we were to throttle it may
be best to make it multi threaded with a single concurrent stream per end
