In last year's summit there was a presentation from Instaclustr -
https://www.instaclustr.com/meetups/presentation-by-ben-bromhead-at-cassandra-summit-2014-san-francisco/.
It could be the solution you are looking for. However I don't see the code
being checked in or JIRA being created. So for now
Usually this is about tuning, and this isn't an uncommon situation for new
users.
Potential steps to take
1) reduce stream throughput to a point that your cluster can handle it.
This is probably your most important tool. The default throughput depending
on version is 200mb or 400mb, go ahead and
Thanks for the reply. The bootstrap of new node put a heavy burden on the
whole cluster and I don't know why. So that' the issue I want to fix
actually.
On Mon, Jan 12, 2015 at 6:08 AM, Eric Stevens migh...@gmail.com wrote:
Yes, but it won't do what I suspect you're hoping for. If you disable
Yes, bootstrapping a new node will cause read loads on your existing nodes
- it is becoming the owner and replica of a whole new set of existing
data. To do that it needs to know what data it's now responsible for, and
that's what bootstrapping is for.
If you're at the point where bootstrapping
Yes, my cluster is almost full and there are lots of pending tasks. You
helped me a lot and thank you Eric~
On Thu, Jan 22, 2015 at 11:59 AM, Eric Stevens migh...@gmail.com wrote:
Yes, bootstrapping a new node will cause read loads on your existing nodes
- it is becoming the owner and replica
Yes, but it won't do what I suspect you're hoping for. If you disable
auto_bootstrap in cassandra.yaml the node will join the cluster and will
not stream any old data from existing nodes.
The cluster will now be in an inconsistent state. If you bring enough
nodes online this way to violate your
