I am using operator version:1.3 and application version: 3.11.6. I am using 2 data centers with same number of nodes.Will cass-operator supports disaster recovery. If supports how to achieve it?
Bringing together the Apache Cassandra experts from the community and DataStax.
Want to learn? Have a question? Want to share your expertise? You are in the right place!
Not sure where to begin? Getting Started
Your question is too open-ended for us to be able to provide a meaningful answer but I'll try my best to respond based on some assumptions.
The concept of disaster recovery (DR) is an old paradigm that is rooted in near-obsolete practices when an organisation's infrastructure was geographically distributed to just 2 or 3 locations. A remote DC classified as a DR site would get activated in the event of a catastrophic failure at the primary site. These days, most organisation cannot tolerate interruptions to their business operations and so have their systems running active-active all the time.
A multi-DC cluster in Cassandra operates in active-active fashion -- there is no primary, there is no secondary. All DCs receive writes from the application(s) in real-time. If DC1 is unavailable (for whatever reason), the remaining DCs continue to operate and the traffic gets diverted to the operational DCs.
Specifically with the cass-operator, when a node goes down, the operator will attempt to automatically recover the statefulsets (STS) provided the outage isn't due to a failure in the underlying infrastructure (e.g. physical host servers going down). Jim Dickinson will correct me if I'm mistaken but there is a limitation with Kubernetes at this point where multi-region deployments isn't a supported feature so clusters can only be deployed to a single-region right now. Cheers!
6 People are following this question.