cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alain RODRIGUEZ <arodr...@gmail.com>
Subject Re: Duplicating a cluster with different # of disks
Date Thu, 06 Aug 2015 20:58:50 GMT
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 cassandra.yaml at the node level.

C*heers,

Alain

2015-08-06 22:41 GMT+02:00 Jeff Jirsa <Jeff.Jirsa@crowdstrike.com>:

> 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: Gerard Maas
> Reply-To: "user@cassandra.apache.org"
> Date: Thursday, August 6, 2015 at 9:50 AM
> To: "user@cassandra.apache.org"
> Subject: Duplicating a cluster with different # of disks
>
> Hi,
>
> I'm currently trying to duplicate a given keyspace on a new cluster to run
> some analytics on it.
>
> My source cluster has 3 disks and corresponding data directories (mnt,
> mnt2, mnt3) but the machines in my target cluster only have 2 disks (mnt,
> mnt2).
>
> What should be the correct procedure to copy the sstable data  from source
> to destination in this case?
>
> -kr, Gerard.
>

Mime
View raw message