what's referencing all the memory.
On Fri, May 6, 2011 at 12:25 PM, Serediuk, Adam
adam.sered...@serialssolutions.com wrote:
We're troubleshooting a memory usage problem during batch reads. We've spent
the last few days profiling and trying different GC settings. The symptoms
We're troubleshooting a memory usage problem during batch reads. We've spent
the last few days profiling and trying different GC settings. The symptoms are
that after a certain amount of time during reads one or more nodes in the
cluster will exhibit extreme memory pressure followed by a gc
Having a well known node configuration that is trivial (one step) to create is
your best maintenance bet. We are using 4 disk nodes in the following
configuration:
disk1: boot_raid1 os_raid1 cassandra_commit_log
disk2: boot_raid1 os_raid1 cassandra_data_dir_raid0
disk3: cassandra_data_dir_raid0
I just ran a test and we do not see that behavior with dynamic snitch disabled.
All nodes appear to be doing local reads as expected.
On May 3, 2011, at 10:37 AM, Jonathan Ellis wrote:
Do you still see this behavior if you disable dynamic snitch?
On Tue, May 3, 2011 at 12:31 PM, Serediuk
heavily loaded than the others, and are correctly pushing queries
to other replicas.
On Tue, May 3, 2011 at 12:47 PM, Serediuk, Adam
adam.sered...@serialssolutions.com wrote:
I just ran a test and we do not see that behavior with dynamic snitch
disabled. All nodes appear to be doing local