>
> Erick, a question purely as a point of curiosity. The entire model of a
> commit log, historically (speaking in RDBS terms), depended on a notion of
> stable store. The idea being that if your data volume lost recent writes,
> the failure mode there would be independent of writes to the
>
> I am still having problems reproducing this, so I am wondering if I have
> created the tables correctly to create this issue.
Paul, I've since had clarification on the bug and I hope I can explain it
correctly here (happy to be corrected if anyone else has insight on the
issue). When you
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.11.6.
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
The Cassandra team is pleased to announce the release of Apache
Cassandra version 3.0.20.
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
The Cassandra team is pleased to announce the release of Apache
Cassandra version 2.2.16.
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
What does
http://cassandra.apache.org/doc/latest/tools/sstable/sstablemetadata.html show
as the type in the upgraded table? Also, the ticket mentions serialization
ordering being incorrect between single and multi-cell column data.
Perhaps there needs to be other non-PK fields to trigger this
I was curious and did some digging. 400k is the max read IOPs on the 1-device
instance types, 3M IOPS is for the 8-device instance types.
From: Reid Pinchback
Reply-To: "user@cassandra.apache.org"
Date: Friday, February 14, 2020 at 11:24 AM
To: "user@cassandra.apache.org"
Subject: Re: AWS
I’ve seen claims of 3M IOPS on reads for AWS, not sure about writes. I think
you just need a recent enough kernel to not get in the way of doing multiqueue
operations against the NVMe device.
Erick, a question purely as a point of curiosity. The entire model of a commit
log, historically
The risk is you violate consistency while you run repair
Assume you have three replicas for that range, a b c
At some point b misses a write, but it’s committed on a and c for quorum
Now c has a corrupt sstable
You empty c and bring it back with no data and start repair
Then the app reads at
Erick,
Thank you for your help.
I am still having problems reproducing this, so I am wondering if I have
created the tables correctly to create this issue.
I have looked at the sstabledumps and they seem exactly the same.
This is the pre upgrade version 3.0.14 ( a snapshotted version )
10 matches
Mail list logo
