I only did in-place conversions from DSE to Apache Cassandra, but after altering the replication scheme I later dropped those keyspaces after the fact. You can keep them there on Apache, they'll just be fallow and taking up space. Not even that much space anyway. Don't forget to change the authenticator, authorizer, and role manager. It will fail to even start if you don't.
On Wed, Jul 24, 2019, 6:45 PM Rahul Reddy <rahulreddy1...@gmail.com> wrote: > This is temporary migration > stratergy > > On Wed, Jul 24, 2019, 6:22 PM Jonathan Koppenhofer <j...@koppedomain.com> > wrote: > >> To clarify... you have 2 datacenters with Datastax, and you want to >> expand to a third DC with Opensource Cassandra? Is this a temporary >> migration strategy? I would not want to run in this state for very long. >> >> For Datastax, you should reach out to their support for questions. >> However, speaking from experience, these are required and will be created >> upon restart of DSE nodes. Even worse, they use custom replication >> strategies (EverywhereStrategy), that will prevent open source from >> working, or the nodes from even starting. You can update EverywhereStrategy >> to Network topology strategy, but be forewarned it will reset back to >> EverywhereStrategy when you simply restart a Datastax node. >> >> Long story short, use Datastax support for info on their product, and be >> very careful. Also note I don't have specific experience with your exact >> scenario. >> >> (My experience with Datastax is version 4.6-5.0) >> >> On Wed, Jul 24, 2019, 10:34 AM Rahul Reddy <rahulreddy1...@gmail.com> >> wrote: >> >>> Hello, >>> >>> I have 2 data centers with dse Cassandra added new DC with apache >>> Cassandra . Dse_perf,dse_systen,dse_security,dse_leases keypsaces created >>> as well . Can we delete them ? >>> >>
