> Whether or not this is likely to happen with Cassandra I don't know. I > don't know much about the incremental duty cycles are scheduled and it > may be the case that Cassandra is not even remotely close to having a > problem with incremental mode.
I should further weaken my statement by pointing out that I never did any exhaustive tweaking to get around the problem (other than disabling incremental mode, since my primary goal has tended to be ensure low pause times and not so much even GC activity). It may be the case that even in stressful cases where it fails by default it is simply a matter of tweaking. So, I guess I should re-phrase: In terms of just turning on incremental mode without at least application specific tweaking (if not deployment specific testing), I would suggest caution. -- / Peter Schuller
