Re: nodetool listsnapshots and auto snapshots from dropped tables

2021-08-10 Thread Erick Ramirez
Awesome! Thanks, mate! 🍻 >

Re: nodetool listsnapshots and auto snapshots from dropped tables

2021-08-10 Thread James Brown
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 they

Re: New Servers - Cassandra 4

2021-08-10 Thread Erick Ramirez
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: New Servers - Cassandra 4

2021-08-10 Thread onmstester onmstester
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: Large number of tiny sstables flushed constantly

2021-08-10 Thread Erick Ramirez
Is it possible that you've got memtable_cleanup_threshold set in cassandra.yaml with a low value? It's been deprecated in C* 3.10 ( CASSANDRA-12228 ). If you do have it configured, I'd recommend removing it completely and restart C* when you ca

Re: nodetool listsnapshots and auto snapshots from dropped tables

2021-08-10 Thread Erick Ramirez
Dropped tables used to be handled differently and were no longer tracked once they were dropped. The clearsnapshot command was fixed (CASSANDRA-6418 ) but listsnapshots doesn't appear to be (for whatever reason). It looks like an oversight to me

Large number of tiny sstables flushed constantly

2021-08-10 Thread Jiayong Sun
Hello, everyone, We have a large cluster with the following info:Cassandra version: 3.11.6Multi-DC and 100 nodes per DC. We recently have seen many nodes with hundreds of thousands tiny sstables flushed to disk constantly. We can see the following messages in debug.log:DEBUG [NativePoolCleaner]

nodetool listsnapshots and auto snapshots from dropped tables

2021-08-10 Thread James Brown
I've noticed that auto snapshots from dropped tables don't seem to show up in `nodetool listsnapshots` (even though they *do* get cleared by `nodetool clearsnapshot`). Is there any reason for this? It's kind of weird that the only way to discover auto-snapshots from dropped tables is to manually ls

Re: User defiend type storage

2021-08-10 Thread Jeff Jirsa
It gets saved in the schema table as a part of the schema. On Tue, Aug 10, 2021 at 8:48 AM Roy Burstein wrote: > Hi , > When creating UDT for a table,does C* store the UDT definition for each > type saved on disk? > Thanks, > Roy >

User defiend type storage

2021-08-10 Thread Roy Burstein
Hi , When creating UDT for a table,does C* store the UDT definition for each type saved on disk? Thanks, Roy

Re: Validation of NetworkTopologyStrategy data center name in Cassandra 4.0

2021-08-10 Thread Jens Fischer
Thanks for providing the links Erick, very helpful. Although it is slightly inconvenient for me I now better understand the motivation. On 10. Aug 2021, at 10:27, Erick Ramirez mailto:erick.rami...@datastax.com>> wrote: You are correct. Cassandra no longer allows invalid DC names for NetworkTo

Re: Validation of NetworkTopologyStrategy data center name in Cassandra 4.0

2021-08-10 Thread Erick Ramirez
You are correct. Cassandra no longer allows invalid DC names for NetworkTopologyStrategy in CREATE KEYSPACE or ALTER KEYSPACE from 4.0 ( CASSANDRA-12681 ). FWIW, here is the NEWS.txt

Validation of NetworkTopologyStrategy data center name in Cassandra 4.0

2021-08-10 Thread Jens Fischer
Hi, in Cassandra 3.11.x I was able to create key spaces with basically arbitrary names for the data center. When I do this with Cassandra 4.0 I get a "ConfigurationException: Unrecognized strategy option {} passed to NetworkTopologyStrategy for keyspace ”. This breaks some unit tests in our CI