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
Hi Community,
We currently have a 3-node Cassandra 3.11 production cluster that was
initially set up with the following configuration:
-
*Snitch:* endpoint_snitch: SimpleSnitch
-
*Keyspace replication:* {'class': 'SimpleStrategy',
'replication_factor&#x
st ID Rack
UN cassandra-0.cassandra.cassandra-jos.svc.cluster.local 365.09 GiB
256 ? 5c3d3b46-300d-49f2-b01d-cbdb44d98022 rack1
UN cassandra-12.cassandra.cassandra-jos.svc.cluster.local 365.68 GiB
256 ? 1d3ed71f-18b4-4cc0-9c6e-3a5479328496 rac
d-settings.html#configSetKernelParameters
>
> JDK: latest JDK17 build, if you are looking for low latency you can try to
> use Shenandoah or ZGC instead of G1 but they can be more sensitive to
> overload/load spikes
> Cassandra yaml: to get the best performance by using the latest features
> (such as
The Cassandra team is pleased to announce the release of Cassandra GoCQL
Driver version 2.0.0-rc1.
The Source release is available here:
https://dlcdn.apache.org/cassandra/cassandra-gocql-driver/2.0.0-rc1/
You can add the driver to your project with the "v2.0.0-rc1" tag:
go get
of G1 but they can be more sensitive to
overload/load spikes
Cassandra yaml: to get the best performance by using the latest features
(such as trie memtables, direct IO commit log, etc) create your
cassandra.yaml from cassandra_latest.yaml configuration.
The default logback configuration is ok from
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
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&
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
Hi Everyone,
I plan to start a POC on Cassandra 5.0.4 as a NoSQL database in our
Production environment.
I'd like to make sure it's well tuned from the start, and I wanted to know
if there are any recommendations for tuning Cassandra, such as:
- Is 5.0.4 a stable version to use in
Hi,
I would like to invite Cassandra users, developers and enthusiasts to
attend Community Over Code North America where we will have a 3-day track
dedicated to Apache Cassandra! The conference this year will be held in
Minneapolis, Minnesota from September 11-14, 2025.
The Cassandra program is
Hello Cassandra community!
Just a reminder that tomorrow we’ll be hosting the Cassandra Contributor
Meeting. We’re excited to have Patrick McFadin joining us to share the
latest updates on ACID transactions.
See details below.
*Speaker*: Patrick McFadin
*Topic*: Update on Cassandra ACID
I am working on using Idempotency within ActiveMQ Classic using Apache
Cassandra as my in-memory store
I have the following jar files that are loaded with ActiveMQ:
camel-cassandraql-4.10.4.jar
cassandra-driver-core-3.10.0.jar
java-driver-core-4.17.0.jar
java-driver-shaded.guava-25.1-jre-graal
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.0.18.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
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 go
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.
Hi all, was curious to the experiences of those who installed/are running in
prod on JDK 17. I understand JDK 17 is quite well baked at this point, but
still listed as "experimental" support-wise, so was curious to hear about some
real-life experiences with it. Thanks,
geremy
IMPORTANT NOTICE:
@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
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
invest
Hi everyone,
We’re looking at the Apache Cassandra Sidecar project
(https://github.com/apache/cassandra-sidecar), our security team has asked us
in the event of a vulnerability being found, would that be disclosed via the
github security advisory system, or would it be disclosed via another
Hi Everyone,
AxonOps is doing a support Apache Cassandra webinar for you to bring your
problems and questions! This isn’t affiliated with the Apache Foundation but
we’ll be discussing whatever problems you feel like bringing up. Should be
helpful if you need assistance.
Join Hayato Shimizu
The Cassandra team is pleased to announce the release of Apache
Cassandra version 4.1.9.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
Hello community,
A Cassandra cluster exists consisting of 4 Datacenters with 22 Cassandra node
each.
A datacenter removal was executed for maintenance purposes.
Before the datacenter removal a repair operation has been triggered to achieve
synchronization of the data before the datacenter
Hi,
I wanted to send a gentle reminder that the deadline for submissions to
Community Over Code 2025 closes in 1 week at 23:59 UTC on April 21, 2025.
Please submit your proposal via
https://sessionize.com/community-over-code-na-2025
Thanks to all who have submitted so far. Feel free to reach out
The Cassandra team is pleased to announce the release of Apache
Cassandra version 5.0.4.
Apache Cassandra is a fully distributed database. It is the right
choice when you need scalability and high availability without
compromising performance.
http://cassandra.apache.org/
Downloads of source
ote for
5.0.4 is complete, and I've squashed any bugs that pop up in my tests.
Jon
[1] https://github.com/rustyrazorblade/easy-cass-lab
On Wed, Apr 9, 2025 at 10:12 AM Geremy Cohen wrote:
> Hi, I was curious if there is a roadmap for graduating JDK17 support for
> Cassandra 5.x f
Hi, I was curious if there is a roadmap for graduating JDK17 support for
Cassandra 5.x from experimental to production ready?
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privileged. If you are not the intended recipient,
please notify the
Tomorrow, I'm starting another data modeling series that assumes starting
with version 5. The last time I did something this comprehensive was for
Cassandra 3. Needless to say, there have been a LOT of updates since then.
There will be five parts, and each one has its own signup for the
I'm now wondering how your Cassandra is starting with this table
configuration, Part of migrating from 3.x should have dropped COMPACT
STORAGE from your tables.
Do you find any notice of exceptions with Cassandra starting up?was the
Description of table1 that you shared from the cu
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
l media post. It all counts. If you
need help, just hit me up on email or slack.Happy to assist in any way.
Patrick
On Thu, Mar 20, 2025 at 6:28 AM Josh McKenzie wrote:
> You may find the charts on the following JIRAs interesting:
> https://issues.apache.org/jira/browse/CASSANDRA-17240
&g
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
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
(CassandraTableRepairManager.java:74)
If you check this:
https://github.com/apache/cassandra/blob/cassandra-4.0/src/java/org/apache/cassandra/db/repair/CassandraTableRepairManager.java#L72
There is if (force || !cfs.snapshotExists…)
So if “force” is “false”, which is the case in case repair is global
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
<https://issues.apache.org/jira/browse/CASSANDRA-20291>) . Since the
FailureDetector primarily relies on the
Dear Wiliam,
I'm also sorry for my poor english !
Compression ratio 0.566… I guess it means If you have 1MB data on your laptop,
you get 0.566MB in Cassandra.
If you put blobs in the table, it is ok!
If it is plain english text, It seams low.
I understand answer of below questions from
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
While it's true that COMPACT STORAGE was deprecated in Cassandra 4.0+, it was not removed. It's largely supported and works just fine for many use cases. Feedback from users indicated that removing it entirely
would be disruptive because it required special effort from Cassandra users
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
William,
Longtime listener, first time poster.
Something stands out here for me. This table uses COMPACT STORAGE which is
deprecated in Cassandra 4.x and it was a hold-over from the old thrift
API. I'm sure that this is eliciting some gasps from the mailing list.
You might actually be b
h McKenzie
> wrote:
>
>> You may find the charts on the following JIRAs interesting:
>> https://issues.apache.org/jira/browse/CASSANDRA-17240
>> <https://issues.apache.org/jira/browse/CASSANDRA-17240?jql=project%20%3D%20CASSANDRA%20and%20text%20~%20%27trie%20memtables%27&g
You may find the charts on the following JIRAs interesting:
https://issues.apache.org/jira/browse/CASSANDRA-17240
<https://issues.apache.org/jira/browse/CASSANDRA-17240?jql=project%20%3D%20CASSANDRA%20and%20text%20~%20%27trie%20memtables%27>
That covers the memtables. The combination of UC
Stephane and Fabian,
Good morning and thank you for your replies. Your English is fine. I just
appreciate the help.
Apache Cassandra was overkill for this application, and this was just something
handed to me. The reason why this is an issue is because of the limited amount
of disk space
Hi,
Could you give more details about the use of tables and modeling about
this single node cassandra ?
Have you began to use Cassandra with 3 version or have you already
migrate before from previous version ( 2.x) ?
To be honest, i would suggest to use the last release avalable, and to
Hi ,
Has anyone able to make fapolicy with Cassandra 4 on RHEL9 .
We tried but we see that initially it took a fresh 3 node cluster to spin
up around 3 hours. Initially schema pull does not happen and eventually
everything starts connecting.
Anyone has setup fapolicy?
Please advise.
Thanks
FMH
Sent: Wednesday, March 19, 2025 3:14 PM
To: Cassandra Support-user
Subject: [External]Cassandra 5.0: Any Official Tests Supporting 'Free
Performance Gains'
This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links
and attachments.
Please report all suspicio
As I'm evaluating to upgrade to C* 4 or 5, one statement caught my
attention for the 5 release (
https://cassandra.apache.org/_/blog/Apache-Cassandra-5.0-Announcement.html):
"Trie Memtables and Trie SSTables These low-level optimizations yield
impressive gains in memory usage a
have one table in a keyspace that is occupying 84.1GB of disk space:
ls -l /var/lib/cassandra/data/keyspace1/table1
…
-rw-rw-r--. 1 x 84145170181 Mar 18 08:28 nb-163033-big-Data.db
…
Regards,
William Crowell
From: William Crowell via user
Date: Friday, March 14, 2025 at 10:53 AM
Hi everyone
We are trying to perform vector search with additional conditions and faced
several issues with that. Could you please clarify is that behavior of the
Cassandra is intended by design, are we doing something wrong, or probably
there is some bug?
Our case:
We need to get a result
Hey Tibor - this was recently brought up in ASF Slack, fix is in review:
CASSANDRA-19902
Hallo everyone,
I’ve just started off testing Cassandra 5.0 for production purposes and I’ve
found an “interesting” change: during bootstrap (joining or replacing a dead
node), it seems nodetool cannot reach the server until the bootstrap has
completed:
Mar 14 15:57:16 *** cassandra[65339
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
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:
snapshot_before_compaction: false
auto_snapshot: true
incremental_backups: false
The only other configuration parameter that had been
e.g. when
incremental_backups is set to true
* mixing repaired and unrepaired sstables, which is usually caused by
incremental repairs, even if it had only been ran once
* partially upgraded cluster, e.g. mixed Cassandra version in the same
cluster
* token ring change (e.g. adding or removing nodes) without
Upgrading From Cassandra 3.x.x to 4.1.3
Dear William,
As Luciano mentioned previously, could you check the snapshot folder?
To know where the data is stored, check the value of data_file_directories in
the cassandra.yaml file.
By default, it is located in the $CASSANDRA_HOME/data/data directory.
You
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
@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
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:
@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
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.
>
>
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
tarball. The artifacts should be universal.– Scott—MobileOn Mar 12, 2025, at 8:22 AM, Fred Habash wrote:Any confirmation or feedback will be appreciated. Thanks On Tue, Mar 11, 2025 at 3:07 PM Fred Habash <fmhab...@gmail.com> wrote:Trying to understand when Apache Cassandra started supporti
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. I do a compaction once a week and take a snapshot
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
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
Trying to understand when Apache Cassandra started supporting ARM-64
architecture. Specifically, AWS Graviton. I have found multiple
documentation comparing C* performance on Intel vs. ARM. But, without
version details.
My understanding is that to run C* on ARM-64, we must use C* >=
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
pecially
> 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 Forward. Come check
>>
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 Bernardo Botella
> wrote:
> >
> > This is a huge milesto
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
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.
>
>
>
The Cassandra team is pleased to announce the release of Apache Sidecar
Cassandra version 0.1.0.
Downloads of source and binary distributions are available here:
https://dlcdn.apache.org/cassandra/cassandra-sidecar/0.1.0/
The Maven artifacts can be found at:
https://repo.maven.apache.org
ed and have used for years in my performance
> evaluations. I've used this combination of tools extensively over the
> years. Most recently, to provide all the performance analysis for
> CASSANDRA-15452.
>
> https://github.com/rustyrazorblade/easy-cass-stress
> https://github.com/ru
the performance analysis for
CASSANDRA-15452.
https://github.com/rustyrazorblade/easy-cass-stress
https://github.com/rustyrazorblade/easy-cass-lab
https://issues.apache.org/jira/browse/CASSANDRA-15452
* nosqlbench is maintained by datastax, is very flexible, can test more
than just Cassandra, but
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
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,
--
Hi Everyone!
My team is evaluating new database solutions and Cassandra is one of the
options we are considering
I would appreciate your guidance on a couple of points:
- *Stable Version Recommendation:* Which Cassandra version is currently
considered the most stable and production-ready
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
Hello, I am a developer from ZTE company. Our project is using your Cassandra
4.1 series version, but the openjdk version still only supports jdk8 and jdk11.
I would like to ask when the new version of Cassandra will support jdk20 and
above. Thank you
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
Hey Cassandra users!
If you're running Cassandra in production, there are some major
changes coming that will significantly change how you operate and
develop with it. I’ll be hosting Cassandra Forward 2025 on March 11
and 12 to walk through these changes from the people building them. I
ra
Cassandra process itself then I would try to decompose the
memory usage: as Jon mentioned the default and expected configuration for
Java heap is Xmx=Xms + -XX:+AlwaysPreTouch, so the memory for Java heap is
allocated in advance and not changing dynamically from OS point of view if
the settings are
s [3], which
> shows how to use it as well as other tools.
>
> Jon
>
> [1] https://issues.apache.org/jira/browse/CASSANDRA-19987
> [2] https://www.man7.org/linux/man-pages/man8/vmstat.8.html
> [3]
> https://netflixtechblog.com/linux-performance-analysis-in-60-000-milliseconds-ac
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 apply to
>>> your question.
>>>
>>> The key to success with stor
s in 60,000 Milliseconds [3], which shows how to use it
as well as other tools.
Jon
[1] https://issues.apache.org/jira/browse/CASSANDRA-19987
[2] https://www.man7.org/linux/man-pages/man8/vmstat.8.html
[3]
https://netflixtechblog.com/linux-performance-analysis-in-60-000-milliseconds-accc10403c5
red way is heap dump, because it will tell you exactly what
caused the memory usage spike, not just confirm or rule out one guess at
a time.
I hope this helps.
Cheers,
Bowen
On 26/02/2025 12:27, vignesh s wrote:
*Setup:*
I have a Cassandra cluster running in 3 datacenters with 3 nodes each
(to
*Setup:*
I have a Cassandra cluster running in 3 datacenters with 3 nodes each
(total 9 nodes), hosted on GCP.
• *Replication Factor:* 3-3-3
• *Compaction Strategy:* LeveledCompactionStrategy
• *Heap Memory:* 10 GB (Total allocated memory: 32 GB)
• *Off-heap Memory:* around 4 GB
• *Workload
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 la
ll 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 file from disk. Sometimes, and in the harder case to
> manage, at the same time. Storage sy
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
ng-apache-cassandra-with-amazon-ebs/>
.
Long Pan 于2025年2月20日周四 14:27写道：
> Hi Cassandra Community,
>
> I’m exploring the feasibility of running Cassandra with remote storage,
> primarily *block storage* (e.g., AWS EBS, OCI Block Volume, Google
> Persistent Disk) and possibly eve
Hi Cassandra Community,
I’m exploring the feasibility of running Cassandra with remote storage,
primarily *block storage* (e.g., AWS EBS, OCI Block Volume, Google
Persistent Disk) and possibly even *file storage* (e.g., NFS, EFS, FSx).
While local SSDs are the typical recommendation for optimal
Hi Folks,
I wanted to give a heads up to the AxonOps MasterClass webinars we are running
on a regular 4-6 weekly basis.
We have our 4th going out on 26th February, here are the details.
Topic: Cassandra + Kafka = Perfect Data Partners
Registration: https://us02web.zoom.us/webinar
The Cassandra team is pleased to announce the release of Cassandra Java
Driver version 4.19.0. This release includes a large number of bug fixes
and improvements representing the work of many contributors. Thanks to
everyone who made this release possible!
The Source release and Binary
Severity: moderate
Affected versions:
- Apache Cassandra 4.0.16
Description:
Privilege Defined With Unsafe Actions vulnerability in Apache Cassandra. An
user with MODIFY permission ON ALL KEYSPACES can escalate privileges to
superuser within a targeted Cassandra cluster via unsafe actions to
/yprngr9cmp9c43m1c56thv1v0v6y5ywq
[2] - https://lists.apache.org/thread/hc9shwlm1kmxdxosbh3qo2xooqoo3sc6
On Mon, Feb 3, 2025 at 6:19 PM Paulo Motta wrote:
>
> Severity: moderate
>
> Affected versions:
>
> - Apache Cassandra 3.0.0 through 3.0.30
> - Apache Cassandra 3.1.0 through 3.11.17
> - Apache
The Cassandra team is pleased to announce the release of Apache Cassandra
version 4.0.17.
This release is a critical security release, fixing an issue found in [1]
and addressing CVE-2025-23015 [2].
Release 4.0.16 intended to fix CVE-2025-23015[2] but did not. This
release 4.0.17 does
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.11.19.
This release contains a fix to performance regression found in [1].
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without
The Cassandra team is pleased to announce the release of Apache Cassandra
version 3.0.32.
This release contains a fix to performance regression found in [1].
Apache Cassandra is a fully distributed database. It is the right choice
when you need scalability and high availability without
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
1 - 100 of 17174 matches
Mail list logo
