What's configuration of following parameters
memtable_flush_queue_size:
concurrent_compactors:
2013/10/30 Piavlo lolitus...@gmail.com
Hi,
Below I try to give a full picture to the problem I'm facing.
This is a 12 node cluster, running on ec2 with m2.xlarge instances (17G
ram , 2 cpus).
We ran into similar heap issues a while ago for 1.0.11, I am not sure
whether you are at the luxury of upgrading to at-least 1.2.9, we were not.
After a lot of various painful attempts and weeks of testing (just as in
your case) the following settings worked (did not completely relieve the
heap
On 10/30/2013 11:34 AM, Jason Tang wrote:
What's configuration of following parameters
memtable_flush_queue_size:
concurrent_compactors:
memtable_flush_queue_size: 4
concurrent_compactors: 1
Lokking at the metrics I did not see FlushWriter pending issues
as well the compactions are keeping up
On 10/30/2013 03:21 PM, srmore wrote:
We ran into similar heap issues a while ago for 1.0.11, I am not sure
whether you are at the luxury of upgrading to at-least 1.2.9, we were
not. After a lot of various painful attempts and weeks of testing
(just as in your case) the following settings
Hi,
Below I try to give a full picture to the problem I'm facing.
This is a 12 node cluster, running on ec2 with m2.xlarge instances (17G
ram , 2 cpus).
Cassandra version is 1.0.8
Cluster normally having between 3000 - 1500 reads per second (depends on
time of the day) and 1700 - 800 writes
