Re: Guidance on Migrating from SimpleSnitch and SimpleStrategy in Cassandra 3.11 Cluster

Hi Nick 1. Take Backup. 2. Migrate the snitch. Refer https://docs.datastax.com/en/cassandra-oss/3.x/cassandra/operations/opsSwitchSnitch.html and https://dba.stackexchange.com/questions/314862/how-do-i-change-the-cassandra-topology-snitch-in-a-multi-az-cluster 3. For altering the keyspace, run alt

Re: POC on Cassandra 5.0.4

Thanks a lot guys :-) Much appreciated! On Mon, Jul 14, 2025 at 1:39 PM Dmitry Konstantinov wrote: > Hi Shalom, > > Yes, 5.0.4 is production ready. > On OS level it makes sense to start from > https://docs.datastax.com/en/dse/6.9/managing/configure/recommended-settings.html#configSetKernelParam

Re: POC on Cassandra 5.0.4

Hi Shalom, Yes, 5.0.4 is production ready. On OS level it makes sense to start from https://docs.datastax.com/en/dse/6.9/managing/configure/recommended-settings.html#configSetKernelParameters JDK: latest JDK17 build, if you are looking for low latency you can try to use Shenandoah or ZGC instead

Re: POC on Cassandra 5.0.4

Hi Shalom We are also using 5.0.4 and I can say that it's a stable version for use in production. We started switching from on-prem to k8s cassandra --> k8ssandra operator 4 years ago so the answer maybe a bit different from what you are looking for. But since you are quite familiar with it since

Re: POC on Cassandra 5.0.4

Hi Manish, :-) I'm quite proficient with Cassandra. I was managing Cassandra clusters for over 5 years. However, I switched jobs and only several years later was I able to persuade my manager to run a POC on Cassandra. :-) I stopped at 3.11 and I'm sure a lot has changed since then. I'd like the P

Re: POC on Cassandra 5.0.4

Hi Yes 5.0.4 is stable version for use in production. You can refer https://cassandra.apache.org/doc/latest/cassandra/getting-started/production.html for production settings. Regards Manish On Sun, Jul 13, 2025 at 11:52 PM Shalom Sagges wrote: > Hi Everyone, > > I plan to start a POC on Cassan

Re: JDK 17 official support -- coming in v5 (or sooner?)

html?utm_source=chatgpt.com > -- > *From:* Dmitry Konstantinov > *Sent:* Wednesday, July 9, 2025 3:33 AM > *To:* user@cassandra.apache.org > *Subject:* Re: JDK 17 official support -- coming in v5 (or sooner?) > > Yes, there is nothing specially applied in

Re: JDK 17 official support -- coming in v5 (or sooner?)

AM To: user@cassandra.apache.org Subject: Re: JDK 17 official support -- coming in v5 (or sooner?) Yes, there is nothing specially applied in 5.0.5 code/config for this purpose, it is only a doc change actually. I can update the website to reflect the doc change but it may take some time (like 1

Re: JDK 17 official support -- coming in v5 (or sooner?)

now you are all busy, any ETA when this >>>> doc update will be completed? >>>> -- >>>> *From:* Dmitry Konstantinov >>>> *Sent:* Tuesday, July 8, 2025 1:48 PM >>>> *To:* user@cassandra.apache.org >>>

Re: JDK 17 official support -- coming in v5 (or sooner?)

- >>> *From:* Dmitry Konstantinov >>> *Sent:* Tuesday, July 8, 2025 1:48 PM >>> *To:* user@cassandra.apache.org >>> *Subject:* Re: JDK 17 official support -- coming in v5 (or sooner?) >>> >>> Hi, we have discussed it alrea

Re: JDK 17 official support -- coming in v5 (or sooner?)

-- >> *From:* Dmitry Konstantinov >> *Sent:* Tuesday, July 8, 2025 1:48 PM >> *To:* user@cassandra.apache.org >> *Subject:* Re: JDK 17 official support -- coming in v5 (or sooner?) >> >> Hi, we have discussed it already in >> https://lists.apache.org/t

Re: JDK 17 official support -- coming in v5 (or sooner?)

pleted? > -- > *From:* Dmitry Konstantinov > *Sent:* Tuesday, July 8, 2025 1:48 PM > *To:* user@cassandra.apache.org > *Subject:* Re: JDK 17 official support -- coming in v5 (or sooner?) > > Hi, we have discussed it already in > https://lists.apache.org/thread/rjdzyx9yz

Re: JDK 17 official support -- coming in v5 (or sooner?)

Thanks Dmitry, very cool. I know you are all busy, any ETA when this doc update will be completed? From: Dmitry Konstantinov Sent: Tuesday, July 8, 2025 1:48 PM To: user@cassandra.apache.org Subject: Re: JDK 17 official support -- coming in v5 (or sooner?) Hi

Re: JDK 17 official support -- coming in v5 (or sooner?)

Hi, we have discussed it already in https://lists.apache.org/thread/rjdzyx9yzm8365t7thgw7wngts46px6n thread. https://issues.apache.org/jira/browse/CASSANDRA-20681 The remaining step is to update the site. Best regards, Dmitry On Tue, 8 Jul 2025 at 21:42, Jon Haddad wrote: > I don't have the thr

Re: JDK 17 official support -- coming in v5 (or sooner?)

I don't have the thread handy but I thought we decided to do this already and it would just be a doc change. Either way, I'm +1 on removing experimental flag. Jon On Tue, Jul 8, 2025 at 1:38 PM Geremy Cohen wrote: > Hi all, just curious as to when docs will be updated to signify official > JDK

Re: Recycled-Commitlogs

> knowledge of a Cassandra item.____ >> __ __ >> Time to unsubscribe >> __ __ >> *From:* Josh McKenzie >> *Sent:* Tuesday, July 1, 2025 1:47 PM >> *To:* user@cassandra.apache.org >> *Subject:* Re: Recycled-Commitlogs >> __ __ >> EXTERNAL

Re: Recycled-Commitlogs

fr not sharing the > knowledge of a Cassandra item. > > > > Time to unsubscribe > > > > *From:* Josh McKenzie > *Sent:* Tuesday, July 1, 2025 1:47 PM > *To:* user@cassandra.apache.org > *Subject:* Re: Recycled-Commitlogs > > > > EXTERNAL > > Can

RE: Recycled-Commitlogs

: Tuesday, July 1, 2025 1:47 PM To: user@cassandra.apache.org Subject: Re: Recycled-Commitlogs EXTERNAL Can anyone explain WHAT they are? Yes Marc. The Scylla community. That's what we're trying to tell you. As far as anyone on this list seems to think, this isn't related to Apache Cas

Re: Recycled-Commitlogs

ain WHAT they are? If they were done away with in > Cassandra then they must have been surplus to requirements. In which case, > why have them originally? They must have been there for some reason. > > *From:* Josh McKenzie > *Sent:* Monday, June 30, 2025 4:16 PM > *To:* us

RE: Recycled-Commitlogs

@cassandra.apache.org Subject: Re: Recycled-Commitlogs EXTERNAL As it is (generally) Cassandra compatible I naturally assumed that these items were in both applications. For future reference - it's "generally CQL API compatible". That's the extent of it. It's analogous to drivin

Re: Recycled-Commitlogs

ly) Cassandra compatible I naturally > > assumed that these items were in both applications. > > > > Marc > > > > From: Jeff Jirsa > > Sent: Thursday, June 26, 2025 7:35 PM > > To: user@cassandra.apache.org > > Cc: user@cassandra.apache.org > &g

RE: Recycled-Commitlogs

atible I naturally assumed that > these items were in both applications. > > Marc > > From: Jeff Jirsa > Sent: Thursday, June 26, 2025 7:35 PM > To: user@cassandra.apache.org > Cc: user@cassandra.apache.org > Subject: Re: Recycled-Commitlogs > > EXTER

RE: Recycled-Commitlogs

atible I naturally assumed that > these items were in both applications. > > Marc > > From: Jeff Jirsa > Sent: Thursday, June 26, 2025 7:35 PM > To: user@cassandra.apache.org > Cc: user@cassandra.apache.org > Subject: Re: Recycled-Commitlogs > > EXTER

RE: Recycled-Commitlogs

@cassandra.apache.org Subject: Re: Recycled-Commitlogs EXTERNAL What version of cassandra is this? Recycling segments was a thing from like 1.1 to 2.2 but really very different in modern versions (and cdc / point in time backup mirrors some of the concepts around hanging onto segments) Knowing the

Re: Recycled-Commitlogs

> cdc / point in time backup mirrors some of the concepts around hanging onto > segments That was my first thought but we never prepended "Recycled-" on the front of that that I know of. On Thu, Jun 26, 2025, at 1:35 PM, Jeff Jirsa wrote: > > What version of cassandra is this? > > Recycling s

Re: Recycled-Commitlogs

What version of cassandra is this? Recycling segments was a thing from like 1.1 to 2.2 but really very different in modern versions (and cdc / point in time backup mirrors some of the concepts around hanging onto segments)Knowing the version would be super helpful though Is this … 1.2? 2.0?On Jun 2

Re: Recycled-Commitlogs

I guess it comes from the archive of commitlogs ，just guess~~~ But I think we need the cassandra's version and commitlog's configuration in cassandra.yaml, and commitlog_archiving.properties to determine this. Marc Hoppins 于2025年6月26日周四 16:08写道： > Hi, > > > > I am not a data person but a Linux

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

is > not a limit there. > > > > Best, > > Raymond Yu > > > > *From: *Jon Haddad > *Date: *Thursday, June 12, 2025 at 12:50 PM > *To: *user@cassandra.apache.org > *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS > > *This Message

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

Thank you for your email. I will get back to you soon.

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

: user@cassandra.apache.org Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS This Message is From an External Sender Caution: Do not click links or open attachments unless you recognize the sender and know the content is safe. I completely missed that this ECS != EKS. My brain

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

al, given an existing Cassandra EC2 footprint and experience >> deploying in that fashion, we’re looking for points for or against >> deploying Cassandra on ECS if in-house tooling is also needed, as outside >> opinions were desired. >> >> >> >> Best, >>

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

t; Best, > > Raymond Yu > > > > > > > > *From: *daemeon reiydelle > *Date: *Thursday, June 12, 2025 at 9:42 AM > *To: *user@cassandra.apache.org > *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS > > *This Message is From an Extern

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

. Best, Raymond Yu From: daemeon reiydelle Date: Thursday, June 12, 2025 at 9:42 AM To: user@cassandra.apache.org Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS This Message is From an External Sender Caution: Do not click links or open attachments unless you recognize the

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

What operator are you all using?  We've just been using statefulsets for our clusters.  I'm a big time on-hardware fan, but an issue with Cassandra is the notion of one JVM per about 1 to 2TBytes of disk space.  Most large servers are in the 256 core+ / 100+TBytes of disk.  Managing that many i

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

June 12, 2025 at 7:16 AM > *To: *user@cassandra.apache.org > *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS > > *This Message is From an External Sender* > Caution: Do not click links or open attachments unless you recognize the > sender and know the

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

t; *From: *Jon Haddad > *Date: *Thursday, June 12, 2025 at 7:16 AM > *To: *user@cassandra.apache.org > *Subject: *Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS > > *This Message is From an External Sender* > Caution: Do not click links or open attachments unle

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

:16 AM To: user@cassandra.apache.org Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS This Message is From an External Sender Caution: Do not click links or open attachments unless you recognize the sender and know the content is safe. I agree that managing Cassandra on

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

in the Cassandra community from the K8ssandra operator, we have significantly more worries with using an in-house one. From: Jon Haddad Date: Thursday, June 12, 2025 at 7:16 AM To: user@cassandra.apache.org Subject: Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS This Message is From

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

I agree that managing Cassandra on Kubernetes can be challenging without prior experience, as understanding all the nuances of Kubernetes takes time. However, there are ways to address the rescheduling issues, node placement, and local disk concerns that were mentioned. You can pin pods to specifi

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

Quick correction on my previous message — I assumed you were referring to running Cassandra on Kubernetes, not purely ECS. Many of the same concerns still apply. ECS tasks can also be rescheduled or moved between instances, which poses risks for Cassandra’s rack awareness and replica distribution.

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

I usually advise against running Cassandra (or most databases) inside Kubernetes. It might look like it simplifies operations, but in my experience, it tends to introduce more complexity than it solves. With Cassandra specifically, Kubernetes may reschedule pods for reasons outside your control (e

Re: Request for Thoughts on Deployments on AWS EC2 vs. ECS

It's possible to manage Cassandra well both with VMs and containers. As you'd be running one container per VM, there is no significant advantage for containers. K8s provides nice tooling and some methodological enforcement which brings order to the setup but if the team aren't top notch experts in

Re: (JOB) MySQL DBA in Denmark

ok Thanks & Best Regards Henry PAN Sr. Lead Cloud Architect (425) 802--3975 https://www.linkedin.com/in/henrypan1 On Wed, Jun 4, 2025 at 3:24 AM James Tobin wrote: > Hello, I am working with an employer that is looking to hire a MySQL > DBA in Denmark. Consequently, I had hoped that some me

Re: Behavior of replicas and forwarded requests

Hey Kyle, What version of Cassandra are you running? Can you share the full (anonymized) schema, including keyspace and table definitions? The trace behavior you’re seeing here might be caused by read speculation: https://cassandra.apache.org/doc/5.0/cassandra/developing/cql/ddl.html#spec_retry

Re: Issue replacing a dead node

One last update: After kicking it more, it finally fully joined the cluster. The third time the server was rebooted and after that it eventually reached the UN state. I wish I had kept the link, but I had read that someone had a similar issue joining a node to a cluster with 4.1.x and the answ

Re: Issue replacing a dead node

Some updates after getting back to this. I did hardware tests and could not find any hardware issues. Instead of trying a replace, I went the route of removing the dead node entirely and then adding in a new node. The new node is still joining, but I am hitting some oddities in the log. When j

Re: Behavior of replicas and forwarded requests

On 5/23/25 00:20, Kyle Butt wrote: I have a keyspace that is using the NetworkTopologyStrategy. In one of the data centers, there are 3 nodes, and the replication factor is 3. I would expect that when I make a request to any of the 3 nodes, that node would answer instead of forwarding the requ

Re: Cassandra on JDK 17

Hi All I see this https://issues.apache.org/jira/browse/CASSANDRA-16895 marked as resolved. This JIRA catered to solving reported issues for supporting JAVA17. Shouldn't the experimental flag be removed? Regards Manish On Thu, May 22, 2025 at 11:42 PM Jon Haddad wrote: > I've got 1K nodes in v

Re: Cassandra on JDK 17

I've got 1K nodes in various clusters running on Java 17. I've had great results with Shenandoah, 30GB heap, and off heap trie memtables. Pauses are as advertised, between 1-3ms. With smaller heaps or high throughput you might see the JVM apply pacing - to ensure it can keep up with allocations.

Re: Apache Cassandra Sidecar - Vulnerability Advisory Location

@cassandra.apache.org , Fleming, Jackson Subject: Re: Apache Cassandra Sidecar - Vulnerability Advisory Location EXTERNAL EMAIL - USE CAUTION when clicking links or attachments Hi Jackson, thanks for reaching out. Details on the ASF responsible disclosure process can be found here: https://apache.org/security

Re: Apache Cassandra Sidecar - Vulnerability Advisory Location

Hi Jackson, thanks for reaching out. Details on the ASF responsible disclosure process can be found here: https://apache.org/security/#reporting-a-vulnerability Thanks for your team's proactive attention to responsible disclosure. ASF and Apache Cassandra are happy to triage and investigate any

Re: Issue replacing a dead node

To add on to what Bowen already wrote, if you cannot find any reason in the logs at all, I would retry using different hardware. In the recent past I have seen two cases where strange Cassandra problems were actually caused by broken hardware (in both cases, a faulty memory module caused the i

Re: Issue replacing a dead node

Is it bad to leave the replacement node up and running for hours even when the cluster forgets it for the old node being replaced? I'll have to set the logging to trace. debug produced nothing. I did stop the service, which produced errors in the other nodes in the datacenter since they had ope

Re: Issue replacing a dead node

In my experience, failed bootstrap / node replacement always leave some traces in the logs. At the very minimal, there's going to be logs about streaming sessions failing or aborting. I have never seen it silently fails or stops without leaving any traces in the log. I can't think of anything t

Re: Issue replacing a dead node

I checked all the logs and really couldn't find anything. I couldn't find any sort of errors in dmesg, system.log, debug.log, gc.log (maybe up the log level?), systemd journal...the logs are totally clean. It just stops gossiping all of a sudden at 22GB of data each time, then the old node retu

Re: Issue replacing a dead node

The dead node being replaced went back to DN state indicating the new replacement node failed to join the cluster, usually because the streaming was interrupted (e.g. by network issues, or long STW GC pauses). I would start looking for red flags in the logs, including Cassandra's logs, GC logs,

Re: Issues while joining

The only difference I found is that the new nodes have been installed with Debian-12 and OpenJDK-17 while the rest of the cluster is running on Debian-11 with OpenJDK-11. > On 9. May 2025, at 07:34, Tibor Répási wrote: > > Rechecked that, the upgrade was complete, all nodes are running 5.0.4 a

Re: Issues while joining

Rechecked that, the upgrade was complete, all nodes are running 5.0.4 and the new once trying to join have the same version installed. > On 8. May 2025, at 16:53, C. Scott Andreas wrote: > > Hi Tibor, > > Can you double check the versions in use by all streaming peers? > > I see the "app" mod

Re: Issues while joining

Hi Tibor, Can you double check the versions in use by all streaming peers? I see the "app" module issue you mention and the ClassCastException – but notice the attempt to cast Result.INCOMPATIBLE to Result.SUCCESS. If Result.INCOMPATIBLE is the node's determination, this looks like an attempt t

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:

  1   2   3   4   5   6   7   8   9   10   >