Re: Work in Progress - Bringing it all together in one "Awesome Cassandra" README

This is great! Thank you. On Fri, Jul 27, 2018 at 2:20 AM Rahul Singh wrote: > Hope you all are are having an amazing week. > > I recently updated > *https://github.com/Anant/awesome-cassandra*/. I've been working on this > while organizing the initi

Work in Progress - Bringing it all together in one "Awesome Cassandra" README

Hope you all are are having an amazing week. I recently updated https://github.com/Anant/awesome-cassandra/. I've been working on this while organizing the initial repository of links for a "Cassandra Hub" (Planet Cassandra 2.0) as I organize links on Cassandra and distributed computing (e.g. K

RE: [EXTERNAL] optimization to cassandra-env.sh

This is a very good explanation of CMS tuning for Cassandra: http://thelastpickle.com/blog/2018/04/11/gc-tuning.html (author Jon Haddad has extensive Cassandra experience – a super star in our field) Sean Durity From: Durity, Sean R Sent: Thursday, July 26, 2018 2:08 PM To: user@cassandra.apache

RE: [EXTERNAL] optimization to cassandra-env.sh

Check the archives for CMS or G1 (whichever garbage collector you are using). There has been significant and good advice on both. In general, though, G1 has one basic number to set and does very well in our use cases. CMS has lots of black art/science tuning and configuration, but you can test o

optimization to cassandra-env.sh

Any one has tried to optimize or change cassandra-env.sh in an server installation to make it use more heap size for garbage collection ? Any ideas ? We are having some oom issues and thinking if we have options other than increasing RAM for that node. Regards

Re: cassandro nodes restarts

Thanks for your prompt replies. No the same node is not bouncing over. When you say it is about to tip over: What can we do to stop that ? Also about that error : you guys are correct: it is a warning and might not be contributing to the node bounce issue and it can be removed by changing batch_s

Lost counter updates during Cassandra upgrade 2.2.11 to 3.11.2

Hi, During rolling upgrade of our cluster we noticed that some updates on table with counters were not being applied. It looked as if it depended on whether coordinator handling request was already upgraded or not. I observed similar behavior while using cqlsh and executing queries manually. So

Re: Infinite loop of single SSTable compactions

Few questions What is your maximumcompactedbytes across the cluster for this table ? What’s your TTL ? What does your data model look like as in what’s your PK? Rahul On Jul 25, 2018, 1:07 PM -0400, James Shaw , wrote: > nodetool compactionstats  --- see compacting which table > nodetool cfstats

Re: cassandro nodes restarts

Do the same nodes reboot or is it arbitrary? I’m wondering if it’s an isolated incident related to dat / traffic skew or could happen on any coordinator Rahul On Jul 26, 2018, 12:31 AM -0400, Jeff Jirsa , wrote: > It’s a warning, but probably not causing you problems > > A 20kB batch is a hint th

Re: Why and How is Cassandra using all my ram ?

Hello again, > It's possible that glibc is creating too many memory arenas. Are you > setting/exporting MALLOC_ARENA_MAX to something sane before calling > the JVM? You can check that in /proc//environ. I checked and we have the default value of 4. > I would also turn on -XX:NativeMemoryTracking