Source: medium.com
Migrating Cassandra from one Kubernetes cluster to another without data losCategory: Deployment, Database, Data, Kubernetes, Infrastructure, RabbitMQ
For about the last six months, we have been successfully using the Rook operator to operate the Cassandra cluster in Kubernetes. And that is when we have discovered that the Rook operator is not flexible enough.
In the rest of the article, we will be using the following definitions for Cassandra clusters: Since the Cassandra-current cluster uses localstorage, you cannot migrate its data to a new cluster directly (as is the case, for example, with vSphere volumes). We will create a temporary installation of Cassandra to solve this problem and use it as kind of a buffer to migrate data.
Scale down Cassandra-temporary and Cassandra-current (keep in mind that the operator is still active in this cluster!) to zero.
In the rest of the article, we will be using the following definitions for Cassandra clusters: Since the Cassandra-current cluster uses localstorage, you cannot migrate its data to a new cluster directly (as is the case, for example, with vSphere volumes). We will create a temporary installation of Cassandra to solve this problem and use it as kind of a buffer to migrate data.
Scale down Cassandra-temporary and Cassandra-current (keep in mind that the operator is still active in this cluster!) to zero.
Related Articles
Community Partners
DevOps Careers