Re: [CFP] Community Over Code NA 2025

Just a reminder! The deadline to submit a proposal closes at 6:59 PM 21 Apr 2025 in Central Daylight Time (UTC-05:00) timezone. Jon On Mon, Mar 10, 2025 at 6:51 AM Paulo Motta wrote: > Hi, > > Please see message below with instructions on submitting talk proposals > for Community Over Code 202

Re: SSTable Migration to oa-* Format After Upgrade to 5

Hey Paul Thanks for your help before. I rolled storage_compatibility_mode to UPGRADING and have been upgrading sstables one node at a time for a few days. That works. Just one question: Is it safe to make any schema changes while I am still doing this? All my nodes are yet running version 5, alth

Re: Graduating JDK17 support for Cassandra 5.x from experimental to production ready

Thanks for bringing this up. I've been meaning to for a while now. I'm at the early stages of doing some testing of Java 11 G1GC vs 17 w/ G1GC vs 17 w/ Shenandoah. I plan on sharing my results with the wider community, and if things look good I'll be proposing we remove the experimental label.

Re: Schema Version Mismatch issue

? From: Sartor Fabien (DIN) via user Sent: 09 April 2025 13:50 To: user@cassandra.apache.org Cc: Sartor Fabien (DIN) Subject: RE: Schema Version Mismatch issue EXTERNAL EMAIL - USE CAUTION when clicking links or attachments Hi Soyal, I have encountered similar issues in the

RE: Schema Version Mismatch issue

Hi Soyal, I have encountered similar issues in the past. What has consistently worked for me is performing a rolling restart of all nodes. If you don’t have tools like Ansible or scripts to automate the process, I suggest starting by restarting the node with the problematic schema. That might h

Re: unsubscribe

unsubscribe On Fri, 4 Apr 2025 at 17:23, FERON Matthieu wrote: > >

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

from TTL 0 to 10 days. This might mean that some data are not deleted >> because at some point in time were written with no TTL ( TTL set to 0). >> >> This has occurred in some systems in past. >> >> You may use the sstableexpiredblocker tool to check about this. >> >> >&

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

lliam Crowell > > > > *From: *C. Scott Andreas > *Date: *Friday, March 21, 2025 at 12:21 AM > *To: *user@cassandra.apache.org > *Cc: *user@cassandra.apache.org > *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x > to 4.1.3 > > You don't of

Re: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Performance Gains'

And I would be remiss if I didn't mention this. If you are doing any testing on your own... SHARE! When we say "Your mileage may vary" it's a great contribution to the project to share 1) Your use case 2) How you tested 3) What you found. Blog post. An email to user@. A social media post. It all

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

Michalis, I will check and get back to you. Thank you. Regards, William Crowell From: Michalis Kotsiouros (EXT) via user Date: Thursday, March 20, 2025 at 8:34 AM To: user@cassandra.apache.org Cc: Michalis Kotsiouros (EXT) Subject: RE: Increased Disk Usage After Upgrading From Cassandra 3

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

pache.org ; Stéphane >> Alleaume >> *Cc:* William Crowell ; sc...@paradoxica.net < >> sc...@paradoxica.net>; asf.telli...@gmail.com >> *Subject:* [EXTERNAL] Re: Increased Disk Usage After Upgrading From >> Cassandra 3.x.x to 4.1.3 >> >> Good mornin

Re: Cassandra 4.0.10 snapshot failure during sequential repair

Hi Panagiotis, I know this is most probably super late to answer to given you posted this year and a half ago but anyway … I just stumbled upon this. The stacktrace you posted is interesting. The culprit is at org.apache.cassandra.db.repair.CassandraTableRepairManager.lambda$snapshot$0(Cassand

Re: Batch Queries Timeout When Private IP of a Node Fails in Multi-DC Cassandra 4.1.4

Dear Cassandra Community, I recently observed an issue in our multi-DC setup where batch queries timed out when the private interface of one node went down (CASSANDRA-20291 ) . Since the FailureDetector primarily relies on the public interface

RE: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

ds: $CASSANDRA_HOME/tools/bin/sstabledump -d Another possibility is to load all the SSTables into another Cassandra instance using: $CASSANDRA_HOME/bin/sstableloader Then, check if you get the same data size. Thank you, Best regards, Fabien De : Tasmaniedemon Envoyé : jeudi, 20 mars 2025 0

RE: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

sstableexpiredblocker tool to check about this. BR MK From: William Crowell via user Sent: March 20, 2025 13:58 To: user@cassandra.apache.org Cc: William Crowell ; Sartor Fabien (DIN) ; tasmaniede...@free.fr Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 Stephane and

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

leexpiredblocker tool to check about this. BR MK From: William Crowell via user < user@cassandra.apache.org > Sent: March 20, 2025 13:58 To: user@cassandra.apache.org Cc: William Crowell < wcrow...@perforce.com >; Sartor Fabien (DIN) < fabien.sar...@etat.ge.ch >; tasmaniede...@free.f

Re: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Performance Gains'

dium=member_desktop&rcm=ACoAAADH8b0BGPPXoegOFjqwPOAgOOhyity45Iw Regards, Paul From: Jon Haddad Date: Friday, 21 March 2025 at 4:12 am To: user@cassandra.apache.org Cc: Jiri Steuer (EIT) , fmhab...@gmail.com Subject: Re: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Perf

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

set to 0). > > This has occurred in some systems in past. > > You may use the sstableexpiredblocker tool to check about this. > > > > BR > > MK > > > > *From:* William Crowell via user > *Sent:* March 20, 2025 13:58 > *To:* user@cassandra.apache.org &g

Re: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Performance Gains'

I’m not sure if i shared this to the user list… I’m doing a massive series on C* 5.0 performance and how it relates to node density and cost. First post is up now. http://rustyrazorblade.com/post/2025/03-streaming/ The benefit any given feature depends on a lot of factors. Hardware and workload v

Re: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Performance Gains'

You may find the charts on the following JIRAs interesting: https://issues.apache.org/jira/browse/CASSANDRA-17240 That covers the memtables. The combination of UCS (new

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

ensions = {} AND gc_grace_seconds = 864000 AND max_index_interval = 2048 AND memtable_flush_period_in_ms = 0 AND min_index_interval = 128 AND read_repair = 'BLOCKING' AND speculative_retry = '99p'; */ Regards, William Crowell From: Sartor Fabien (DIN) via us

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

*To: *user@cassandra.apache.org *Cc: *William Crowell , Bowen Song *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 Bowen, This is just a single Cassandra node.  Unfortunately, I cannot get on the box at the moment, but the following configuration is in

RE: [External]Cassandra 5.0: Any Official Tests Supporting 'Free Performance Gains'

Hi FMH, I haven't seen these official tests and that was the reason I did these tests with the official tools. Regards J. Steuer This item's classification is Internal. It was created by and is in property of EmbedIT. Do not distribute outside of the organization. From: FMH Sent: Wednes

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

To: user@cassandra.apache.org Cc: William Crowell , Bowen Song Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 Bowen, This is just a single Cassandra node. Unfortunately, I cannot get on the box at the moment, but the following configuration is in cassandra.yaml

Re: SSTable Migration to oa-* Format After Upgrade to 5

Hi Luciano, It is not a must, as, after the node is upgraded all the new sstables will be created as oa sstables. Then old nb sstables will get compacted away eventually, but this eventually could be a long time in the future. So I would recommend running the sstable upgrade, even if you wait t

Re: SSTable Migration to oa-* Format After Upgrade to 5

Amazing! So this is not a big deal having nodes running on mixed versions of sstables for a while. Thank you ! Luciano Greiner On Tue, Mar 18, 2025 at 12:09 PM Paul Chandler wrote: > > Hi Luciano, > > It is not a must, as, after the node is upgraded all the new sstables will be > created as o

Re: SSTable Migration to oa-* Format After Upgrade to 5

One thing I am not really sure is if upgrading sstables is really a must after the Cassandra 5 upgrade. Thanks Luciano Greiner On Sun, Mar 16, 2025 at 2:33 PM Paul Chandler wrote: > > Yes, that should sort it out. > > Regards > > Paul > Sent from my iPhone > > > On 16 Mar 2025, at 18:34, Lucia

Re: Cassandra 5.0 nodetool availability changes

Hey Tibor - this was recently brought up in ASF Slack, fix is in review: CASSANDRA-19902

Re: SSTable Migration to oa-* Format After Upgrade to 5

Great ,Thanks Scott . בתאריך יום א׳, 16 במרץ 2025, 21:40, מאת C. Scott Andreas ‏< sc...@paradoxica.net>: > Hi Edi, > > Details are in NEWS.txt: > https://github.com/apache/cassandra/blob/cassandra-5.0/NEWS.txt > > – Scott > > On Mar 16, 2025, at 11:37 AM, edi mari wrote: > >  > > Sorry for jump

Re: SSTable Migration to oa-* Format After Upgrade to 5

Hi Edi,Details are in NEWS.txt: https://github.com/apache/cassandra/blob/cassandra-5.0/NEWS.txt– ScottOn Mar 16, 2025, at 11:37 AM, edi mari wrote:Sorry for jumping into the conversation, but I wanted to ask— is there an guide for upgrading Cassandra from v4 to v5? Edi בתאריך יום א׳, 16 במרץ 2025

Re: SSTable Migration to oa-* Format After Upgrade to 5

Sorry for jumping into the conversation, but I wanted to ask— is there an guide for upgrading Cassandra from v4 to v5? Edi בתאריך יום א׳, 16 במרץ 2025, 19:33, מאת Paul Chandler ‏: > Yes, that should sort it out. > > Regards > > Paul > Sent from my iPhone > > > On 16 Mar 2025, at 18:34, Luciano G

Re: SSTable Migration to oa-* Format After Upgrade to 5

Yes, that should sort it out. Regards Paul Sent from my iPhone > On 16 Mar 2025, at 18:34, Luciano Greiner wrote: > > Thank you Paul! > > So should I restart the nodes with UPGRADING mode and run the > upgradesstables again? > > Thank you! > > Luciano Greiner > (54) 996309845 > >> On Sun

Re: SSTable Migration to oa-* Format After Upgrade to 5

Thank you Paul! So should I restart the nodes with UPGRADING mode and run the upgradesstables again? Thank you! Luciano Greiner (54) 996309845 On Sun, Mar 16, 2025 at 2:58 AM Paul Chandler wrote: > > Hi Luciano, > > It sounds like you could have the storage_compatibility_mode set to the > def

Re: SSTable Migration to oa-* Format After Upgrade to 5

Hi Luciano, It sounds like you could have the storage_compatibility_mode set to the default CASSANDRA_4 value, check this and change it to UPGRADING or NONE. Full details can be found in the Cassandra.yaml https://cassandra.apache.org/doc/latest/cassandra/managing/configuration/cass_yaml_file.h

RE: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

the command: find . -iname snapshots -exec du -h {} \; Best regards, Fabien De : William Crowell via user Envoyé : vendredi, 14 mars 2025 10:51 À : user@cassandra.apache.org Cc : William Crowell Objet : Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 PRUDENCE. Ce

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

user Cc: Bowen Song Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 A few suspects: * snapshots, which could've been created automatically, such as by dropping or truncating tables when auto_snapshots is set to true, or compaction

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

A few suspects: * snapshots, which could've been created automatically, such as by dropping or truncating tables when auto_snapshots is set to true, or compaction when snapshot_before_compaction is set to true * backups, which could've been created automatically, e.g. when incremental_backup

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

Sartor and Stéphane, Thank you for your replies. We will check this and get back with you. Regards, William Crowell From: Sartor Fabien (DIN) via user Date: Friday, March 14, 2025 at 6:03 AM To: user@cassandra.apache.org Cc: Sartor Fabien (DIN) Subject: RE: Increased Disk Usage After

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

Stéphane We do not do any repairs and maybe that is the issue. We do a once weekly compaction. Regards, William Crowell From: crystallo...@gmail.com Date: Friday, March 14, 2025 at 5:35 AM To: user@cassandra.apache.org Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

@cassandra.apache.org *Cc: *William Crowell *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 You don't often get email from luciano.grei...@gmail.com. Learn why this is important <https://aka.ms/LearnAboutSenderIdenti

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

that would affect disk > space? > > > > Thank you for your reply, > > > > William Crowell > > > > *From: *Luciano Greiner > *Date: *Thursday, March 13, 2025 at 10:21 PM > *To: *user@cassandra.apache.org > *Cc: *William Crowell > *Subject: *Re:

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

@cassandra.apache.org Cc: William Crowell Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 You don't often get email from luciano.grei...@gmail.com. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> Haven't you forgot to clean some snap

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

am Crowell via user > *Date: *Wednesday, March 12, 2025 at 4:42 PM > *To: *user@cassandra.apache.org > *Cc: *William Crowell > *Subject: *Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x > to 4.1.3 > > I also forgot to include we do compaction once a week. > >

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

Hi, Is this mailing list still active? Thanks. From: William Crowell via user Date: Wednesday, March 12, 2025 at 4:42 PM To: user@cassandra.apache.org Cc: William Crowell Subject: Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3 I also forgot to include we do compaction

Re: Cassandra ARM Support: What Version & What Download Links?

I’m not a Graviton user, but with support for both aarch64 and x86_64, I’d recommend the most recent patchlevel release of 4.0.x or 5.0.x.I don’t see architecture-specific links on the download page — but in any case, architecture-specific libraries would be bundled within the jars in the download

Re: Increased Disk Usage After Upgrading From Cassandra 3.x.x to 4.1.3

I also forgot to include we do compaction once a week. Hi. A few months ago, I upgraded a single node Cassandra instance from version 3 to 4.1.3. This instance is not very large with about 15 to 20 gigabytes of data on version 3, but after the update it has went substantially up to over 100gb

Re: Cassandra ARM Support: What Version & What Download Links?

Any confirmation or feedback will be appreciated. Thanks On Tue, Mar 11, 2025 at 3:07 PM Fred Habash wrote: > Trying to understand when Apache Cassandra started supporting ARM-64 > architecture. Specifically, AWS Graviton. I have found multiple > documentation comparing C* performance on Intel v

Re: Recommended Cassandra Version for POC & AWS EC2 Graviton Compatibility

The standard cassandra-test tool done the job for me. -- Raphael Mazelier Sent from Proton Mail Android Original Message On 3/6/25 18:30, Shalom Sagges wrote: > Thanks a lot for the info Raphael! > > Are there any recommended sysbench/cassandra tests I should look into? > > O

Re: [RELEASE] Apache Cassandra Sidecar 0.1.0 released

Damn.. listing name sucks. Also Saranya and whoever else was involved in this epic milestone! Taking the occasion, happy international women's day to all Cassandrettes 🌹 On Sat, 8 Mar 2025 at 11:24 Paulo Motta wrote: > Congrats on this release! 🍾👏👏 Awesome work to all involved, specially > but

Re: [RELEASE] Apache Cassandra Sidecar 0.1.0 released

Congrats on this release! 🍾👏👏 Awesome work to all involved, specially but not limited to Dinesh, Francisco, Bernado et al 😊 On Fri, 7 Mar 2025 at 16:48 Patrick McFadin wrote: > We happen to have some very informed engineers discussing Sidecar and > the many things you can do with it at Cassandra

Re: [RELEASE] Apache Cassandra Sidecar 0.1.0 released

We happen to have some very informed engineers discussing Sidecar and the many things you can do with it at Cassandra Forward. Come check out the talk and give them a shout-out! https://www.datastax.com/events/cassandra-forward-march-2025 Congrats on the release! On Fri, Mar 7, 2025 at 10:44 AM B

Re: [RELEASE] Apache Cassandra Sidecar 0.1.0 released

This is a huge milestone! It’s incredible to see this release happening. Congrats to everyone involved! > On Mar 7, 2025, at 9:48 AM, Francisco Guerrero wrote: > > The Cassandra team is pleased to announce the release of Apache Sidecar > Cassandra version 0.1.0. > > > Downloads of source and

Re: Recommended Cassandra Version for POC & AWS EC2 Graviton Compatibility

Thanks a lot for the info guys! I really appreciate it 🙏 On Thu, Mar 6, 2025 at 9:05 PM Jon Haddad wrote: > There's several options for load testing. I'll admit that I'm massively > biased as I wrote one of them. > > * easy-cass-stress offers a variety of customizable workloads out of the > box

Re: Recommended Cassandra Version for POC & AWS EC2 Graviton Compatibility

There's several options for load testing. I'll admit that I'm massively biased as I wrote one of them. * easy-cass-stress offers a variety of customizable workloads out of the box and can stress many features without writing any code or learning new config. I wrote this with the goal of getting

Re: Recommended Cassandra Version for POC & AWS EC2 Graviton Compatibility

Thanks a lot for the info Raphael! Are there any recommended sysbench/cassandra tests I should look into? On Thu, Mar 6, 2025 at 12:02 PM Raphael Mazelier wrote: > Cassandra is generally stable. Every version is OK so I would use the > latest. > Regarding Graviton we run most of our clusters on

Re: Recommended Cassandra Version for POC & AWS EC2 Graviton Compatibility

Cassandra is generally stable. Every version is OK so I would use the latest. Regarding Graviton we run most of our clusters on Graviton and we haven't any problem. That said after further analysis the ratio perf/price is not that good. I really advice to use x7a (new AMD cpu). best, -- Raph O

Re: How to fix delta data when reattach EBS async replica?

Hi Blake, CEP-45 can help quite a lot here. Do you think the understanding is correct? What do CEP-45 release timings look like? Will Accord gate it? I appreciate any help you can provide. Jaydeep On Fri, Feb 28, 2025 at 9:40 PM Jaydeep Chovatia wrote: > Thanks, Jeff, for the detailed response

Re: How to fix delta data when reattach EBS async replica?

Also you violate consistency the second it attaches and you can’t run repair offline, so you may serve reads that don’t return expected results (empty or resurrecting, but not respecting monotonic quorum) It’s basically the same as a corrupt volume. If you care about strict data correctness you

Re: [Question]When does Cassandra support OpenJDK 20 and above？

My hope is to have JDK21 support merged in before our next major which we'll likely push to release this calendar year. Work is tracked here: https://issues.apache.org/jira/browse/CASSANDRA-18831 At this point there's a handful of test failures to burn down but otherwise JDK21 support is largel

Re: How to fix delta data when reattach EBS async replica?

Thanks, Jeff, for the detailed response. Overall, it seems there is nothing out of the box available today, and it would require some surgery (either to commitlog or hints) if we even want the two replicas to send the delta mutation. Jaydeep On Fri, Feb 28, 2025 at 6:16 PM Jeff Jirsa wrote: > A

Re: How to fix delta data when reattach EBS async replica?

On 2025/03/01 00:27:27 Jaydeep Chovatia wrote: > Hi, > > I want to reattach an asynchronously replicated EBS volume to Cassandra. I > want to know how to fix the delta inconsistency when reattaching other than > running a repair on the dataset. > > Here is the scenario. > Three Cassandra nodes

Re: Cassandra Memory Spikes - Tuning Suggestions?

The section *"Why does top report that Cassandra is using a lot more memory than the Java heap max?" *on the page https://cassandra.apache.org/doc/latest/cassandra/overview/faq/index.html can provide some useful information. I have seen Cassandra tries to take all the available free RAM using mappe

Re: Cassandra Memory Spikes - Tuning Suggestions?

I would recommend checking first for what exact metric do you have drops: free memory or available memory. There is a common delusion about free vs available memory in Linux: https://www.linuxatemyram.com/ Overwise if you really have spikes in *used* memory and these are spikes in memory used by Ca

Re: Cassandra Memory Spikes - Tuning Suggestions?

Thanks Bowen and Jon for the clarification and suggestions! I will go through them and dig more. Yes, the JVM heap size is fixed and I can see it is allocated at all times. The spikes I am referring to happen in addition to heap allocated memory. I had tuned heap settings to resolve GC pause issue

Re: Seeking Advice on Running Cassandra with Remote Disk

It may help with some, but it's compaction and memtable flushes that generate the most IO. You also run the risk of not having data fully committed to disk if something bad were to happen. It might be ok for time series data that you can afford to lose, but not for mission critical things. On Fri,

Re: Cassandra Memory Spikes - Tuning Suggestions?

Can you explain a bit more what you mean by memory spikes? The defaults we ship use the same settings for min and max JVM heap size, so you should see all the memory allocated to the JVM at startup. Did you change anything here? I don't recommend doing so. If you're referring to files in the pa

Re: Cassandra Memory Spikes - Tuning Suggestions?

Hi vignesh, Correlation does not imply causation. I wouldn't work on the assumption that the memory usage spikes are caused by compactions to start with. It's best to prove the causal effect first. There's multiple ways to do this, I'm just throwing in some ideas: 1. taking a heap dump whil

Re: Seeking Advice on Running Cassandra with Remote Disk

Perhaps a basic question: In the context of a remote disk, wouldn't it make even more sense to use commitlog_sync = periodic rather than batch? Since periodic decouples disk I/O from client write latency, it seems better suited for mitigating the additional overhead of remote storage. On Fri, Feb

Re: Seeking Advice on Running Cassandra with Remote Disk

Thank you all very much, Guo, Patrick and Jon! I will take a close look at the resources you are sharing. On Thu, Feb 20, 2025 at 10:06 AM Patrick McFadin wrote: > I'll give you the general guidance around any type of storage you > pick. This even applies to local disks but it will directly appl

Re: Seeking Advice on Running Cassandra with Remote Disk

I'll give you the general guidance around any type of storage you pick. This even applies to local disks but it will directly apply to your question. The key to success with storage and Cassandra is sequential, concurrent IO. Most of the large IO operations are either writing and reading a large f

Re: Seeking Advice on Running Cassandra with Remote Disk

See the DISCUSS Merging compaction improvements to 5.0 , Jon said he have worked with AWS and the EBS team directly and wrote the Best Practices for C* on EBS

Re: Questions on CEP-21

Hi, responses inline... > On 11 Feb 2025, at 17:36, Long Pan wrote: > > Hey Sam, > The improvements in CEP-21 look awesome. I am currently running Cassandra 4.1 > and plan to upgrade to 5.x in the future, where CEP-21 has been implemented. > I have a few questions: > • I am using the sing

Re: CVE-2025-23015: Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions

A performance regression was detected in the security releases 3.0.31 [1] and 3.11.18 [2]. Users affected by this vulnerability are recommended to upgrade to versions 3.0.32 and 3.11.19 instead. Remaining versions are unaffected. [1] - https://lists.apache.org/thread/yprngr9cmp9c43m1c56thv1v0v6y5

Re: Access to the JIRA

Hi Sebastian, Thank you very much, created an account and bug report as well. And is it possible to be invited to the Slack channel as a guest? With best regards, Artem ср, 5 февр. 2025 г. в 18:19, Sebastian Marsching : > > Hi Artem, > > you can request a JIRA account here: > https://selfserve

Re: Access to the JIRA

Hi Artem, you can request a JIRA account here: https://selfserve.apache.org/jira-account.html Best regards, Sebastian > Am 05.02.2025 um 18:19 schrieb Artem Golovko : > > Hello, > > I would like to report a cassandra bug and would like to have jira account > for that. > > Thanks! smime.p

Re: [RELEASE] Apache Cassandra 3.11.18 released

The Cassandra team have identified a performance regression in releases 3.0.31 and 3.11.18. This regression only affects these specific versions and does not occur in the recent 4.0.16, 4.1.8 or 5.0.3 releases. Users are advised to be aware of this when considering upgrades on the 3.0 and 3.11 li

Re: [RELEASE] Apache Cassandra 3.0.31 released

The Cassandra team have identified a performance regression in releases 3.0.31 and 3.11.18. This regression only affects these specific versions and does not occur in the recent 4.0.16, 4.1.8 or 5.0.3 releases. Users are advised to be aware of this when considering upgrades on the 3.0 and 3.11 li

Re: [RELEASE] Apache Cassandra 4.1.8 released

UNSUBSCRIBE Sent from Yahoo Mail for iPhone On Monday, February 3, 2025, 6:00 PM, Štefan Miklošovič wrote: The Cassandra team is pleased to announce the release of Apache Cassandra version 4.1.8. Apache Cassandra is a fully distributed database. It is the right choice when you need scalab

Re: Cassandra 5 upgrade and Schema Agreement failures

Yes, I would add the 6 new nodes, then decommission the 6 original nodes, then upgrade to 5.0. Remember to change the seed node values before you decommission the old nodes. Thanks Paul > On 30 Jan 2025, at 14:42, Luciano Greiner wrote: > > Ok, so you mean I setup these new 6 nodes as 4.1.3

Re: Cassandra 5 upgrade and Schema Agreement failures

Ok, so you mean I setup these new 6 nodes as 4.1.3, then just upgrade the software, correct? Thank you! Luciano On Thu, Jan 30, 2025 at 6:57 AM Paul Chandler wrote: > > Hi Luciano, > > The problem occurs due to Cassandra 5 making changes to the system tables, so > the cluster will be in schem

Re: Cassandra 5 upgrade and Schema Agreement failures

Hi Luciano, The problem occurs due to Cassandra 5 making changes to the system tables, so the cluster will be in schema mismatch during the upgrade process, until all the nodes are on 5.0 Normally this would not be a problem, as the system tables are not replicated anyway, but, as you are find

Re: Schema agreement check after DDL query is unreliable

Cc: Tommy Stendahl Subject: Re: Schema agreement check after DDL query is unreliable Date: Thu, 16 Jan 2025 10:52:17 + Sorry, wrong list :-) -Original Message- From: Tommy Stendahl via user Reply-To: user@cassandra.apache.org To: user@cassandra.apache.org Cc: Tommy Stendahl Subje

Re: Schema agreement check after DDL query is unreliable

Sorry, wrong list :-) -Original Message- From: Tommy Stendahl via user Reply-To: user@cassandra.apache.org To: user@cassandra.apache.org Cc: Tommy Stendahl Subject: Schema agreement check after DDL query is unreliable Date: Thu, 16 Jan 2025 10:33:32 + Hi, When we upgraded the java

Re: Enable audit log

On Tue, 14 Jan 2025 at 17:02, Andrew Weaver wrote: > I can confirm that on 4.0.x it works as expected because we use this > extensively. > Hi Andrew, that is good to hear. Although i also tried it with the latest 4.0.15 and see worse behaviour: Activating auditlog with nodetool shows in syslog:

Re: Enable audit log

On Tue, 14 Jan 2025 at 17:00, Dmitry Konstantinov wrote: > Hi all, > > > > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 > > I suppose this logic should work during a startup: > https://github.com/apache/cassandra/blob/trunk/src/java/

Re: UNSUBSCRIBE

UNSUBSCRIBE On Tue, 14 Jan 2025 at 19:32, A via user wrote: > UNSUBSCRIBE > > > Sent from Yahoo Mail for iPhone >

Re: UNSUBSCRIBE

> > UNSUBSCRIBE > >

Re: Enable audit log

I can confirm that on 4.0.x it works as expected because we use this extensively. On Tue, Jan 14, 2025, 10:00 AM Jeff Jirsa wrote: > Surprising. Feels like something that should change. If it’s enabled in > yaml, why WOULDNT we want it started on start? > > > > On Jan 14, 2025, at 7:40 AM, Štefa

Re: Enable audit log

Hi all, > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 I suppose this logic should work during a startup: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L109 , shouldn't? It wo

Re: Enable audit log

Surprising. Feels like something that should change. If it’s enabled in yaml, why WOULDNT we want it started on start? > On Jan 14, 2025, at 7:40 AM, Štefan Miklošovič wrote: > > Hi Sebastian, > > the behaviour you see seems to be a conscious decision: > > https://github.com/apache/cassand

Re: Enable audit log

Hi Sebastian, the behaviour you see seems to be a conscious decision: https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/audit/AuditLogManager.java#L204 On Tue, Jan 14, 2025 at 4:21 PM Sebastian Albrecht < sebastian.albre...@agido.com> wrote: > Hi, > i am using cassand

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

On Wed, Dec 18, 2024 at 11:50 AM Paul Chandler wrote: > > This is all old history and has been fixed, so is not really what the > question was about, however these old problems have a bad legacy in the > memory of the people that matter. Hence the push back we have now. > I totally understand th

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

OK, it seems like I didn’t explain it too well, but yes it is the rolling restart 3 times as part of the upgrade that is causing the push back, my message was a bit vague on the use cases because there are confidentiality agreements in place so I can’t share too much. We have had problems in th

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

On Wed, Dec 18, 2024 at 12:26 PM Jeff Jirsa wrote: > I think this is one of those cases where if someone tells us they’re > feeling pain, instead of telling them it shouldn’t be painful, we try to > learn a bit more about the pain. > > For example, both you and Scott expressed surprise at the con

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

On Wed, Dec 18, 2024 at 12:12 PM Jon Haddad wrote: > I think we're talking about different things. > > > Yes, and Paul clarified that it wasn't (just) an issue of having to do > rolling restarts, but the work involved in doing an upgrade. Were it only > the case that the hardest part of doing a

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

I think this is one of those cases where if someone tells us they’re feeling pain, instead of telling them it shouldn’t be painful, we try to learn a bit more about the pain. For example, both you and Scott expressed surprise at the concern of rolling restarts (you repeatedly, Scott mentioned t

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

Yeah, the issue with the yaml being out of sync is consistent with any other JMX change, such as compaction throughput / threads, etc. You'd have to deploy the config and apply the change via JMX otherwise you'd risk restarting the node and running into an issue. I think there's probably room for

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

I think we're talking about different things. > Yes, and Paul clarified that it wasn't (just) an issue of having to do rolling restarts, but the work involved in doing an upgrade. Were it only the case that the hardest part of doing an upgrade was the rolling restart... >From several messages a

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

It's clear from discussion on this list that the current "storage_compatibility_mode" implementation and upgrade path for 5.0 is a source of real and legitimate user pain, and is likely to result in many organizations slowing their adoption of the release. Would love to discuss on dev@ how we can

Re: Cassandra 5 Upgrade - Storage Compatibility Modes

On Wed, Dec 18, 2024 at 11:43 AM Jon Haddad wrote: > > We (Wikimedia) have had more (major) upgrades go wrong in some way, than > right. Any significant upgrade is going to be weeks —if not months— in the > making, with careful testing, a phased rollout, and a workable plan for > rollback. We'd

  1   2   3   4   5   6   7   8   9   10   >