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 <rc...@eventbrite.com> wrote: 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 256M. We are using the >default settings for commitlog_sync, commitlog_sync_period_in_ms and >commitlog_segment_size_in_mb. What version of Cassandra? 1G is tiny for cassandra heap. There is a direct relationship between the data in the commitlog and memtables and in the heap. You almost certainly need more heap or less commitlog. =Rob
