Wow, didn't recognize/expect such fundamental Change in a minor Version. -
But then I can at least say that I have a 21 Node production Cluster
running with all different Versions from 3.11.0 to 3.11.4.
Am Do., 5. März 2020 um 08:09 Uhr schrieb Erick Ramirez <
erick.rami...@datastax.com>:
> Are y
>
> Are you telling me that cassandra changes sstanle file format when
> updating from 3.11.4 to 3.11.5?
>
It was introduced in C* 3.0.18 and 3.11.4. The format changed from -mc- to
-md- because of a bug with min/max clustering values. It had the potential
to result in data loss so there was no ch
Are you telling me that cassandra changes sstanle file format when updating
from 3.11.4 to 3.11.5?
Von meinem iPhone gesendet
> Am 05.03.2020 um 02:05 schrieb Sandeep Nethi :
>
>
> Hi,
>
> I think there is no way to revert sstables to previous version once they are
> upgraded and having new
Hi,
I think there is no way to revert sstables to previous version once they
are upgraded and having new transactions on upgraded version.
But you can try some workarounds by creating a secondary datacenter with
3.11.0 and having the primary datacenter upgraded to 3.11.5. This way if
you come acr
>
> ... the older version of C* will not be able to read the SSTables using
> the old format.
>
Sorry, I meant to say *"... using the NEW format"*. Cheers!
Once you've upgraded to a version of Cassandra that uses a new SSTable
format, you cannot downgrade the binaries -- for whatever reason -- because
the older version of C* will not be able to read the SSTables using the old
format.
I'm more concerned that you think reverting to a .0 release is a be
Hi,
As the SSTable file formats have changed from 3.11.4 to "md "
https://docs.datastax.com/en/landing_page/doc/landing_page/compatibility.html
We are going to take snapshots but still wanted to understand .
After we do upgrades stable when we upgrade from 3.11.0 to 3.11.5 , and
later in future i
