Hello, I can't answer this question about the sstableloader (even though I think it should be ok). My understanding, even though I'm not really up to date with latest Datastax work, is that DSE uses a modified but compatible version of Cassandra, for everything that is not 'DSE feature' specifically. Especially I expect SSTable format to be the same. SSTable loader has always been slow and inefficient for me though I did not use it much.
I think the way out DSE should be documented somewhere in Datastax docs, if not I think you can ask Datastax directly (or maybe someone here can help you). My guess is that the safest way out, without any downtime is probably to perform a datacenter 'switch': - Identify the Apache Cassandra version used under the hood by DSE (5.0.7). Let's say it's 3.11.1 (I don't know) - Add a new Apache Cassandra datacenter to your DSE cluster using this version (I would rather use 3.11.latest in this case though... 3.11.1 had memory leaks and other wild issues). - Move client to this new DC - Shutdown the old DC. I wrote a runbook to perform such an operation not that long ago, you can find it here: https://thelastpickle.com/blog/2019/02/26/data-center-switch.html I don't know for sure that this is the best way to go out of DSE, but that would be my guess and the first thing I would investigate (before SSTableLoader, clearly). Hope that helps, even though it does not directly answers the question (that I'm unable to answer) about SSTable & SSTableLoader compatibility with DSE clusters. C*heers Le mar. 28 mai 2019 à 22:22, Rahul Reddy <rahulreddy1...@gmail.com> a écrit : > Hello, > > Does sstableloader works between datastax and Apache cassandra. I'm trying > to migrate dse 5.0.7 to Apache 3.11.1 ? >
