Re: Cassandra consuming whole RAM (64 G)

Hi All, I applied Cassandra patch for issue 8248 to see what it do. Now I noticed below errors in my system.log : ERROR [NonPeriodicTasks:1] 2015-01-07 10:55:48,869 CassandraDaemon.java:153 - Exception in thread Thread[NonPeriodicTasks:1,5,main] java.lang.AssertionError: null at org.apa

Re: Cassandra consuming whole RAM (64 G)

That even with that patch you'll likely run heap pressure with batches of that size, so either increase your heap and take the GC hit on CPU (and have longer GCs) or don't use large batches. The batch conversation is a bigger one which I discuss here http://lostechies.com/ryansvihla/2014/08/28/cas

Re: Cassandra consuming whole RAM (64 G)

Thanks Ryan... We will keep ur valuable suggestion in resolving this issue.. But what is your take on Cassandra patch for issue 8248 to resolve this. On Tuesday, January 6, 2015, Ryan Svihla wrote: > Btw side note here, you're using GIANT Batches, and the logs are > indicating such, this will ca

Re: Cassandra consuming whole RAM (64 G)

Btw side note here, you're using GIANT Batches, and the logs are indicating such, this will cause a signficant amount of heap pressure. The root cause fix is not to use giant batches in the first place. On Tue, Jan 6, 2015 at 4:43 AM, Rahul Bhardwaj wrote: > Hi Joe.. > > Thanks for your valuabl

Re: Cassandra consuming whole RAM (64 G)

Hi Joe.. Thanks for your valuable solution.. it worked. But for this problem *The processes are killed by kernel, coz they are eating all memory (oom-killer). We have set JAVA heap to default (i.e. it is using 8G) because we have 64 GB RAM.* Should I apply patch given for issue https://issues.

答复: Cassandra consuming whole RAM (64 G)

...@mac.com] 发送时间: 2015年1月6日 15:12 收件人: user@cassandra.apache.org 主题: Re: Cassandra consuming whole RAM (64 G) Thanks Rahul and good luck! I’m really curious to hear what the result is. On Jan 6, 2015, at 2:10 AM, Rahul Bhardwaj wrote: Thanks for your response.. i will get back to you

Re: Cassandra consuming whole RAM (64 G)

Thanks Rahul and good luck! I’m really curious to hear what the result is. > On Jan 6, 2015, at 2:10 AM, Rahul Bhardwaj > wrote: > > Thanks for your response.. i will get back to you with my findings. > > On Tue, Jan 6, 2015 at 12:36 PM, Joe Ramsey > wrote: > That

Re: Cassandra consuming whole RAM (64 G)

Thanks for your response.. i will get back to you with my findings. On Tue, Jan 6, 2015 at 12:36 PM, Joe Ramsey wrote: > That should be “writing too many bytes” not “waiting too many bytes” just > for clarity’s sake. > > On Jan 6, 2015, at 2:03 AM, Joe Ramsey wrote: > > I’m not an expert. Real

Re: Cassandra consuming whole RAM (64 G)

That should be “writing too many bytes” not “waiting too many bytes” just for clarity’s sake. > On Jan 6, 2015, at 2:03 AM, Joe Ramsey wrote: > > I’m not an expert. Really just learning this myself but it looks like > according to the stack you’re getting an exception waiting too many bytes t

Re: Cassandra consuming whole RAM (64 G)

I’m not an expert. Really just learning this myself but it looks like according to the stack you’re getting an exception waiting too many bytes to the commit log. That’s controlled by commit_log_segment_size_in_mb setting. The maximum write size that C* will allow is half of the value set f

Re: Cassandra consuming whole RAM (64 G)

Hi Joe, PFB output of system.log tail -n 100 system.log INFO [CompactionExecutor:164] 2015-01-06 11:58:28,555 CompactionTask.java:251 - Compacted 4 sstables to [/var/lib/cassandra/data/clickstream/im_csl_log-22207f2081bb11e4abd4a9d4f1e0b940/clickstream-im_csl_log.im_csl_log_catalog_owner_glusr_

Re: Cassandra consuming whole RAM (64 G)

Hi Joe, PFA heap dump regards: Rahul Bhardwaj On Tue, Jan 6, 2015 at 11:35 AM, Joe Ramsey wrote: > Did you try generating a heap dump so you can look through it to see > what’s actually happened? > > > On Jan 6, 2015, at 12:58 AM, Rahul Bhardwaj > wrote: > > Hi, > > We are using cassandra

Re: Cassandra consuming whole RAM (64 G)

Did you try generating a heap dump so you can look through it to see what’s actually happened? > On Jan 6, 2015, at 12:58 AM, Rahul Bhardwaj > wrote: > > Hi, > > We are using cassandra 2.1 version in a cluster of three machines each with > 64 GB RAM > > The processes are killed by kernel,

Cassandra consuming whole RAM (64 G)

Hi, We are using cassandra 2.1 version in a cluster of three machines each with 64 GB RAM The processes are killed by kernel, coz they are eating all memory (oom-killer). We have set JAVA heap to default (i.e. it is using 8G) because we have 64 GB RAM. Please help. Regards: Rahul Bhardwaj --