Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Pierre-Yves Ritschard <pyr@spootnik.org>
To: user@cassandra.apache.org
Subject: Re: going back in time
References: 
 <32156_1343136969_500EA4C9_32156_2308_1_9632480C9F82B44294C2302320958E980849EDD383@PUEXCB2F.nanterre.francetelecom.fr>
	<87lii9qnnh.fsf@spootnik.org>
	<30829_1343138425_500EAA79_30829_2886_1_9632480C9F82B44294C2302320958E980849EDD3C0@PUEXCB2F.nanterre.francetelecom.fr>
User-Mail-Address: pyr@spootnik.org
Date: Tue, 24 Jul 2012 16:12:04 +0200
In-Reply-To: 
 <30829_1343138425_500EAA79_30829_2886_1_9632480C9F82B44294C2302320958E980849EDD3C0@PUEXCB2F.nanterre.francetelecom.fr>
	(mdione ext's message of "Tue, 24 Jul 2012 16:00:20 +0200")
Message-ID: <87hasxqmdn.fsf@spootnik.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.95 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<mdione.ext@orange.com> writes:

> De=C2=A0: Pierre-Yves Ritschard [mailto:pyr@spootnik.org]
>> Snapshot and restores are great for point in time recovery. There's no
>> particular side-effect if you're willing to accept the downtime.
>
>   Are you sure? The system KS has no book-keeping about the KSs/CFs?=20
> For instance, schema changes, etc?
>

Don't take my word for it, it's easy enough to fill up a small 3 node
cluster and play with it.

Here's a few more things that you should pay attention to:

- If you change the schema you are obviously going to have to reconverge
  to the previous schema.
- You want to avoid pending commitlog entries. If you want to load a
  full snapshot from scratch, the easiest route would be to drop the KS,
  recreate it with the expected schema and load your sstables from disk.

>> If you don't want to take your whole cluster offline you can use
>> sstableloader as well.
>
>   Sounds wonderful.