I would not suggest to do that, because the new "Archive" node would be a new DC that you would need to build (Operational wise).
You could also snapshot the old one once it finishes and use SSTableloader to push it into your Development DC. This way you have isolation from Production. Plus no operational overhead. Regards, Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin: *linkedin.com/in/carlosjuzarterolo <http://linkedin.com/in/carlosjuzarterolo>* Mobile: +351 918 918 100 www.pythian.com On Mon, Mar 6, 2017 at 10:43 AM, Gábor Auth <auth.ga...@gmail.com> wrote: > Hi, > > The background story: we are developing an MMO strategy game and every two > week the game world ends and we are starting a new one with a slightly > different new database scheme. So that, we have over ~100 keyspaces in our > cluster and we want to archive the old schemes into a separated Cassandra > node or something else to be available online for support of development. > The archived keyspace is mostly read-only and rarely used (~once a year or > less often). > > We've two DC Cassandra cluster with 4-4 nodes, the idea is the following: > we add a new Cassandra node with DC name 'Archive' and change the > replication factor of old keyspaces from {'class': > 'NetworkTopologyStrategy', 'DC01': '3', 'DC02': '3'} to {'class': > 'NetworkTopologyStrategy', 'Archive': '1'}, and repair the keyspace. > > What do you think? Any other idea? :) > > Bye, > Gábor Auth > > -- --
