The StarRocks
Cluster Snapshot feature was introduced in
v3.4.2 and is a core part of the disaster recovery strategy for
shared-data (compute-storage separated) clusters.
Regarding its status and GA plans:
*
Current Status: As of the latest documentation and the StarRocks 3.5 release (August 2025), the feature is still officially labeled as
Beta.
*
Production Readiness: Despite the "Beta" tag, it is heavily promoted in the v3.5 release as a key mechanism for mission-critical disaster recovery. It is designed to capture the full cluster state (metadata and data) in object storage, enabling recovery in minutes.
*
GA Roadmap: There is
no publicly announced date for when it will transition to General Availability (GA). Typically, StarRocks features move to GA after a few minor release cycles of community feedback and stability testing in real-world production environments.
*
Current Focus: The 2025–2026 roadmap continues to emphasize reliability and "automated operations." You can expect the feature to mature as limitations (such as the current "one automated snapshot" limit) are addressed in upcoming versions like 3.5.x or 3.6.
Recommendations:
*
Test in Staging: Since it is beta, it's recommended to validate the restore process thoroughly in a staging environment before relying on it for production DR.
*
Stay Updated: Monitor the
StarRocks GitHub Roadmap or the
#release
channel in Slack for official GA announcements.
If you need help with a specific configuration or a "Cluster Restore" workflow, let me know!
References
•
administration/cluster_snapshot.md
•
deployment/shared_data/feature-support-shared-data.md