Just to add a few additional notes on the in-place replacement.
* We had to remove system.local and system.peers
* Since we remove those system tables, you also have to put
replace_address_first_boot in cassandra-env with the same IP address.
* We also temporarily add the node as a seed to avoid
Jonathan's high level process for in place conversion looks right.
To answer your original question about versioning, DSE release notes lists
the equivalent Cassandra version as 3.11.0.
DataStax Enterprise 5.1.2 -
DataStax Enterprise 5.1.10
Apache Cassandra™ 3.11.0 (updated)
Kind Regards,
An alternative approach is to form another new cluster, leave the original
cluster alive (many times
it's a must since it needs to be 24x7 online). Double write to the two
clusters and later migrate the
data to it. Either by taking a snapshot and pass those files to the new
cluster or with
Thanks, nice summary of the overall process.
Dinesh
On Tuesday, December 4, 2018, 9:38:47 PM EST, Jonathan Koppenhofer
wrote:
Unfortunately, we found this to be a little tricky. We did migrations from DSE
4.8 and 5.0 to OSS 3.0.x, so you may run into additional issues. I will also
Unfortunately, we found this to be a little tricky. We did migrations from
DSE 4.8 and 5.0 to OSS 3.0.x, so you may run into additional issues. I will
also say your best option may be to install a fresh cluster and stream the
data. This wasn't feasible for us at the size and scale in the time
HI All,
we are migrating from DSE to open source Cassandra. if anyone has recently
migrated, Can you please share their experience, steps you followed and
challenges you guys faced.
we want to migrate to the same computable version in open source, can you
give us version number(even with the
