I think you just have to do a "DESC KEYSPACE mykeyspace;" from one node of the production cluster then copy the output and import it in your dev cluster using "cqlsh -f output.cql".
Take care at the start of the output you might want to change DC names, RF or strategy. Also, if you don't want to restart nodes you can load data by using "nodetool refresh mykeyspace mycf" C*heers Alain 2015-06-08 22:42 GMT+02:00 Anton Koshevoy <nowa...@gmail.com>: > Rob, thanks for the answer. > > I just follow instruction from > http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_snapshot_restore_new_cluster.html > > If not to remove system table data, the test cluster starts interfering > to a production cluster. How Can I avoid this situation? > > > > On June 8, 2015 at 9:48:30 PM, Robert Coli (rc...@eventbrite.com) wrote: > > On Mon, Jun 8, 2015 at 6:22 AM, Anton Koshevoy <nowa...@gmail.com> wrote: > >> - sudo rm -rf /db/cassandra/cr/data0*/system/* >> > > This removes the schema. You can't load SSTables for column families which > don't exist. > > =Rob > >
