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 <mailto:joe.r

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 to

Re: Cassandra consuming whole RAM (64 G)

che.cassandra.db.Keyspace.apply(Keyspace.java:351) > ~[apache-cassandra-2.1.2.jar:2.1.2-SNAPSHOT] > at org.apache.cassandra.db.Mutation.apply(Mutation.java:214) > ~[apache-cassandra-2.1.2.jar:2.1.2-SNAPSHOT] > at > org.apache.cassandra.db.MutationVerbHandler.doVerb(Mutat

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,

Re: how wide can wide rows get?

You can have up to 2 billion columns but there are some considerations. This article might be of some help. http://www.ebaytechblog.com/2012/08/14/cassandra-data-modeling-best-practices-part-2/#.VGWdT4enCS0