Re: Large number of tiny sstables flushed constantly

4 flush writers isn't bad since the default is 2. It doesn't make a difference if you have fast disks (like NVMe SSDs) because only 1 thread gets used. But if flushes are slow, the work gets distributed to 4 flush writers so you end up with smaller flush sizes although it's difficult to tell how

Re: New Servers - Cassandra 4

That's 430TB of eggs in the one 4U basket so consider that against your MTTR requirements. I fully understand the motivation for that kind of configuration but *personally*, I wouldn't want to be responsible for its day-to-day operation but maybe that's just me. 

Re: nodetool listsnapshots and auto snapshots from dropped tables

I filed this as CASSANDRA-16843 . I also repro'd it on 4.0.0 just to make sure nobody snuck in a fix. On Tue, Aug 10, 2021 at 6:39 PM Erick Ramirez wrote: > Dropped tables used to be handled differently and were no longer tracked > once

Re: New Servers - Cassandra 4

Hi, What about this type of blades, which gives you about 12 (commodity) servers  in 3U: https://www.supermicro.com/en/products/microcloud Sent using https://www.zoho.com/mail/ On Tue, 03 Aug 2021 02:01:13 +0430 Joe Obernberger wrote Thank you Max.  That is a solid choice. 

Re: nodetool listsnapshots and auto snapshots from dropped tables

Awesome! Thanks, mate!  >

Re: Large number of tiny sstables flushed constantly

Hi Erick, Thanks for your response.Actually we did not set the memtable_cleanup_threshold in the cassandra.yaml.However, we have memtable_flush_writers: 4 defined in the yaml, and VM node has 16-core.Any advice for this param's value? Thanks again.Jiayong SunOn Tuesday, August 10, 2021,

Re: Large number of tiny sstables flushed constantly

Hi Erick, The nodes have 4 SSD (1TB for each but we only use 2.4TB of space. Current disk usage is about 50%) with RAID0. Based on number of disks we increased  memtable_flush_writers: 4 instead of default of 2. For the following we set:- max heap size - 31GB- memtable_heap_space_in_mb (use