Re: best pointers to learn Cassandra maintenance

On Thu, Oct 8, 2020 at 5:31 AM Attila Wind wrote: > Hey Guys, > > We already started to feel that however Cassandra performance is awesome > in the beginning over time > - as more and more data is present in the tables, > - more and more deletes creating tombstones, > - cluster gets here and

Re: best pointers to learn Cassandra maintenance

In Cassandra, "repair" refers to anti-entropy repairs. I think that's where most of the confusion is. DBAs see the word "repair" and think it is a one-off operation to "fix something broken". Users incorrectly think that once it is fixed then there shouldn't be a need to repair again. However in

Re: cassandra tracing's source_elapsed microseconds

> > Does the above indicate it took 20.696 milliseconds to run the last > "Partition index with 0 entries found for sstable 6" activity? > Yes, that's correct. It's cumulative. And the last entry for "Request complete" is the total time it took for the query. Cheers!

cassandra tracing's source_elapsed microseconds

Hi folks, I've been looking at various articles on the TRACING ON output of cassandra. I'm not finding a definitive description of what the output means. https://docs.datastax.com/en/dse/6.7/cql/cql/cql_reference/cqlsh_commands/cqlshTracing.html says "Note: The source_elapsed column value is

Re: Tool for schema upgrades

I second Alex's recommendation. We use https://github.com/patka/cassandra-migration to manage schema migrations in Reaper and it has a consensus feature to prevent concurrent migrations from clashing. Cheers, Alex Le jeu. 8 oct. 2020 à 19:10, Alex Ott a écrit : > Hi > > Look at

Re: Tool for schema upgrades

Hi Look at https://github.com/patka/cassandra-migration - it should be good. P.S. Here is the list of tools that I assembled over the years: - [ ] https://github.com/hhandoko/cassandra-migration - [ ] https://github.com/Contrast-Security-OSS/cassandra-migration - [ ]

Tool for schema upgrades

Hi all, Can anyone recommend a tool to perform schema DDL upgrades, that follows best practice to ensure you don’t get schema mismatches if running multiple upgrade statements in one migration ? Thanks Paul - To unsubscribe,

RE: Reducing no. of nodes to 0 without losing data

Tried persistence as well (just table schemas, no data). It works as well across restarts. Next challenge for me is to find out how to backup the data in case there is a cluster wide data loss. Sent from Mail for Windows 10 From: Manu

RE: Reducing no. of nodes to 0 without losing data

Dear Christopher I tried the answer and it works (at least the stopping bit). I still need to test persistence bit which to be honest might take time considering that I am more rubbish in K8S than Cassandra. I had created an question on SO. Please feel free to provide your answer there.

best pointers to learn Cassandra maintenance

Hey Guys, We already started to feel that however Cassandra performance is awesome in the beginning over time - as more and more data is present in the tables, - more and more deletes creating tombstones, - cluster gets here and there not that well balanced performance can drop quickly and

RE: Reducing no. of nodes to 0 without losing data

The operator doesn’t accept 0. Changing the size in example-cass-dc-minimal.yaml doesn't work as I get error `The CassandraDatacenter "dc1" is invalid: spec.size: Invalid value: 1: spec.size in body should be greater than or equal to 1` Sent from