Graham,
Thanks for the reply. As I stated in mine first mail increasing the heap size
fixes the problem but I'm more interesting in figuring out the right properties
for commitlog and memtable sizes when we need to keep the heap smaller.
Also I think we are not seeing CASSANDRA-7546 as I apply
Hi all,
We have a node with commit log director ~4G. During start-up of the node on
commit log replaying the used heap space is constantly growing ending with OOM
error.
The heap size and new heap size properties are - 1G and 256M. We are using the
default settings for commitlog_sync,
On Tue, Aug 12, 2014 at 9:34 AM, jivko donev jivko_...@yahoo.com wrote:
We have a node with commit log director ~4G. During start-up of the node
on commit log replaying the used heap space is constantly growing ending
with OOM error.
The heap size and new heap size properties are - 1G and
Hi Robert,
Thanks for your reply. The Cassandra version is 2.07. Is there some commonly
used rule for determining the commitlog and memtables size depending on the
heap size? What would be the main disadvantage when having smaller commitlog?
On Tuesday, August 12, 2014 8:32 PM, Robert Coli
Agreed need more details; and just start by increasing heap because that may
wells solve the problem.
I have just observed (which makes sense when you think about it) while testing
fix for https://issues.apache.org/jira/browse/CASSANDRA-7546, that if you are
replaying a commit log which has a
