Treat this scenario as any node replacement/restore and test out the
typical backup methods or bulk data loading to see what works best for
you. Look at container volume mounts on the host system to possibly
simplify procedures on the same host system. If moving the container to
a different host system, general linux data movement utilities are many
and varied.
Depending on the restore method, schema treatment may differ, for
instance a snapshot will have a `schema.cql` file contained in the
snapshot directory that can be used. Other methods may require schema
creation, then data restore.
https://cassandra.apache.org/doc/latest/operating/backups.html
https://cassandra.apache.org/doc/latest/operating/bulk_loading.html
Hope that gets you started on some things to try. Depending on what you
choose and specific questions along the way may define where to best get
help - for docker volume mount strategies, the best help may be some
docker mailing list or irc channel, for example, but definitely evaluate
the different cassandra utilities and ask away if you get stuck on one.
Kind regards,
Michael
On 6/13/20 11:57 AM, Manu Chadha wrote:
Hi
I create a Cassandra Container, run it, create schema and add data to
it. When I later stop the Container and delete it and create a new one
from the image, the previously created schema and data is lost.
Can I/How can I persist data and schema such that whenever a container
is created from an image, it picks existing schema and data?
Do would I have to recreate the schema and add data?
Thanks
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
