haproxy should be fine. normal GCs aren't a problem, you don't need to worry about that. what is a problem is when you shove more requests into cassandra than it can handle, so it tries to GC to get enough memory to handle that, then you shove even more requests, so it GC's again, and it spirals out of control and "freezes."
https://issues.apache.org/jira/browse/CASSANDRA-685 will address this by not allowing more requests than it can handle. On Sat, Feb 20, 2010 at 10:22 AM, Simon Smith <simongsm...@gmail.com> wrote: > I'm still in the experimentation stage so perhaps forgive this hypothetical > question/idea. I am planning to load balance by putting haproxy in front of > the cassandra cluster. First of all, is that a bad idea? > > Secondly, if I have high enough replication and # of nodes, is it possible > and a good idea to proactively cause GCing to happen? (I.e. take a node out > of the haproxy LB pool, somehow cause it to gc, and then put the node back > in... repeat at intervals for each node?) > > Simon Smith >
