So, are you saying this is normal and expected from Cassandra? So, under load, we can expect java garbage collection to stop the Cassandra process on that server from time to time, essentially taking out the node for short periods of time while it does garbage collection?
Also, why is there so much garbage collection to begin with? Memcache uses a slab allocator to reuse blocks to prevent allocation/deallocation of blocks from consuming all the cpu time. Are there any plans to reuse blocks so the garbage collector doesn't have to work so hard? Paul On 3/7/2011 4:35 PM, Jonathan Ellis wrote: > It sounds like you're complaining that the JVM sometimes does stop-the-world > GC. > > You can mitigate this but not (for most workloads) eliminate it with > GC option tuning. That's simply the state of the art for Java garbage > collection right now. > > On Sun, Mar 6, 2011 at 2:18 AM, ruslan usifov <ruslan.usi...@gmail.com> wrote: >> >> 2011/3/6 aaron morton <aa...@thelastpickle.com> >>> Your node is under memory pressure, after the GC there is still 5.7GB in >>> use. In fact it looks like memory usage went up during the GC process. >>> >>> Can you reduce the memtable size, caches or the number of CF's or increase >>> the JVM size? Also is this happening under heavy load ? >>> >> Yes I do bulk load to cluster >> >> >> I reduce memtable to 64MB sutuation became better, but it is all the same >> very rare GC more than 15 Sec happens. Can reduce >> flush_largest_memtables_at helps? O may be some GC options? >> > >
