This happened with version 3.11.10.
We were analyzing impact until now as this happened only on our production
systems. There was probably not enough concurrency on our staging environments
so it did not happen there.
We will start to write a reproducer and file an issue afterwards.
Thanks for
If you don't have an explicit goal of dropping compact storage, it's not necessary to as a
prerequisite to upgrading to 4.x+. Development community members recognized that
introducing mandatory schema changes as a prerequisite to upgrading to 4.x would increase
operator + user overhead and limi
This sounds a lot like cassandra-13004 which was fixed, but broke data being
read-repaired during an alter statement
I suspect it’s not actually that same bug, but may be close/related.
Reproducing it reliably would be a huge help.
- Jeff
> On May 7, 2024, at 1:50 AM, Matthias Pfau via user
Hi there,
we just ran drop compact storage in order to prepare for the upgrade to version
4.
We observed that column values have been written as null, if they where
inserted while the drop compact storage statement was running. This just
happened for the couple seconds the drop compact storage
