We use NetworkTopologyStrategy as the replication strategy. The only DSE specific features we use (left untouched by default) are: authenticator: com.datastax.bdp.cassandra.auth.DseAuthenticator authorizer: com.datastax.bdp.cassandra.auth.DseAuthorizer role_manager: com.datastax.bdp.cassandra.auth.DseRoleManager
So I hope by changing these to the COSS recommended ones, before the migration, DSE will be able to switch to them on its own (?) and then do the final transition of tarball installation. Thank you all for your answers! On Tue, Aug 15, 2017 at 10:42 PM, Jon Haddad <jonathan.had...@gmail.com> wrote: > I agree with Jeff, it’s not necessary to launch a new cluster for this > operation. > > On Aug 15, 2017, at 7:39 PM, Jeff Jirsa <jji...@gmail.com> wrote: > > Or just alter the key space replication strategy and remove the DSE > specific strategies in favor of network topology strategy > > > -- > Jeff Jirsa > > > On Aug 15, 2017, at 7:26 PM, Erick Ramirez <flightc...@gmail.com> wrote: > > Ioannis, it's not a straightforward process to migrate from DSE to COSS. > There are some parts of DSE which are not recognised by COSS, e.g. > EverywhereStrategy for replication only known to DSE. > > You are better off standing up a new COSS 3.11 cluster and restore app > keyspaces to the new cluster. Cheers! > > On Wed, Aug 16, 2017 at 6:33 AM, Ioannis Zafiropoulos <john...@gmail.com> > wrote: > >> Hi all, >> >> We have setup a new cluster DSE 5.1.2 (with Cassandra 3.11.0.1758) and we >> want to migrate it to Apache Cassandra 3.11.0 without loosing schema or >> data. >> >> Anybody, has done it before? >> >> Obviously we are going to test this, but it would be nice to hear if >> somebody else has gone through with the procedure. >> >> Thank you! >> > > >
