Re: Duplicating a cluster with different # of disks

2015-08-12 Thread Gerard Maas
Many thanks for confirming the procedure. I was doing the copy from 3->2 as explained before. My doubt came from noticing that the total count strongly differed from src to destination. 3M vs 150k. But small test tables with few hundred records all went well. Double checked the copy and the proce

Re: Duplicating a cluster with different # of disks

2015-08-06 Thread Alain RODRIGUEZ
I agree with Jeff, those 2 solution should work well indeed to have distinct cluster (data will be fixed in time, not synchronised). It really depends on you but basically having hybride data storage structures is not an issue at all in both cases as it is something that you can set in the cassand

Re: Duplicating a cluster with different # of disks

2015-08-06 Thread Alain RODRIGUEZ
I forget to specify that you will obtain 2 DC instead of 2 cluster, the main differences are that DCs are connected through gossip and keep synced (make sure your clients are sticked to your main DC). Depending on what you want to achieve you might want 2 clusters or 2 DC. 2015-08-06 22:31 GMT+02:

Re: Duplicating a cluster with different # of disks

2015-08-06 Thread Jeff Jirsa
You can copy all of the sstables into any given data directory without issue (keep them within the keyspace/table directories, but the mnt/mnt2/mnt3 location is irrelevant). You can also stream them in via sstableloader if your ring topology has changed (especially if tokens have moved) From

Re: Duplicating a cluster with different # of disks

2015-08-06 Thread Alain RODRIGUEZ
Hi Gerard, You should probably add a new datacenter following this procedure : http://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_dc_to_cluster_t.html You will just have to make sure to configure all the nodes of the new nodes to use mnt + mnt2 instead of mnt + mnt2 + mnt3. M