If you want all of the instances to be consistent with each other, this is much harder, but if you only want a container that can stop and resume, you don't have to do anything more than flush + snapshot the storage. The data files on cassandra should ALWAYS be in a state where the database will restart, because they have to be to tolerate power outage.
On Tue, Nov 10, 2020 at 3:39 PM Florin Andrei <flo...@andrei.myip.org> wrote: > Running Apache Cassandra 3 in Docker. I need to snapshot the storage > volumes. Obviously, I want to be able to re-launch Cassandra from the > snapshots later on. So the snapshots need to be in a consistent state. > > With most DBs, the sequence of events is this: > > - flush the DB to disk > - "freeze" the DB > - snapshot the storage > - "unfreeze" the DB > > What does that sequence translate to, in Cassandra parlance? > > What is the sequence of events that needs to happen when I bring the DB > up from an old snapshot? Will there be a restore procedure, or can I > just start it as usual? > > -- > Florin Andrei > https://florin.myip.org/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > >
