Cluster Switching Data Consistency via Priority-Based Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cluster switching methods in cloud storage systems face challenges in ensuring data consistency and minimizing user impact during inter-cluster data migration or backup, with asynchronous synchronization causing latency and data inconsistency, and synchronous synchronization affecting user access rates and delays.
Innovation Solution
A method and device for cluster switching that synchronizes original data from a first cluster to a second cluster, setting the original data priority lower and new data priority higher, allowing higher-priority data to overwrite lower-priority data, and using message queues for write and delete operations to maintain data consistency during switching.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If asynchronous synchronization is used to copy data from primary cluster to secondary cluster, then data consistency is ensured, but user write access is blocked during switching causing latency and usage impact
Solution Approach 1:
The system performs data synchronization in advance before cluster switching is triggered. The asynchronous synchronization module continuously copies data from the primary cluster to the secondary cluster beforehand, so that when switching occurs, the secondary cluster already has up-to-date data ready, eliminating the need to block user write access during switching.
Solution Approach 2:
An asynchronous synchronization module acts as an intermediary between the primary and secondary clusters. This module handles data copying in the background without interfering with user operations on either cluster, allowing write access to continue uninterrupted while maintaining data consistency through continuous background synchronization.
2Ease of operation
If synchronous synchronization is used to write data to both primary and secondary clusters, then switching is simple, but user access successful rate decreases and delays increase
Solution Approach 1:
Data is synchronized to the secondary cluster in advance through asynchronous operations before switching is needed. This preliminary action ensures that when switching occurs, the secondary cluster is already prepared with current data, eliminating the need for time-consuming synchronous writes during user operations.
Solution Approach 2:
The asynchronous synchronization module operates continuously in the background, maintaining constant data flow from primary to secondary cluster without interrupting user operations. This continuous background action ensures data is always up-to-date on the secondary cluster without causing access delays.
3Reliability
If write access is blocked on primary cluster during synchronization, then data inconsistency problem is solved, but user usage is affected
Solution Approach 1:
The asynchronous synchronization module serves as an intermediary that handles data copying in the background without requiring user write access to be blocked. It continuously monitors and copies data changes from the primary cluster to the secondary cluster, maintaining consistency while allowing uninterrupted user operations.
Solution Approach 2:
Data synchronization is performed in advance and continuously in the background before any switching operation. This preliminary synchronization ensures that the secondary cluster has current data ready, eliminating the need to block user write access on the primary cluster during switching.
4Productivity
If data is copied to secondary cluster before switching, then seamless switching is achieved, but ensuring data consistency during the copy process becomes challenging
Solution Approach 1:
The asynchronous synchronization module implements a feedback mechanism where it continuously monitors data changes on the primary cluster and automatically copies them to the secondary cluster. This real-time feedback loop ensures that the secondary cluster remains synchronized with the primary cluster throughout the copying process, maintaining data consistency even as data is being transferred.
Solution Approach 2:
Data synchronization operates continuously without interruption during the cluster switching process. The asynchronous module maintains constant data flow from primary to secondary cluster, ensuring that even as data is being copied and switched, consistency is maintained through uninterrupted background synchronization.
Data Source
AI summary
Apparatuses and methods are disclosed for cluster switching. An exemplary method may include synchronizing original data on a first cluster to a second cluster after starting to switch clusters. A priority of the original data on the second cluster is set to a lower priority. The method may also include responding to a write operation request on the second cluster in the period of synchronizing the original data on the first cluster to the second cluster. A priority of new data corresponding to the write operation request is set to a higher priority. A version of data with a higher priority can overwrite another version of data. The method may further include responding to the write operation request on the second cluster after synchronizing the original data on the first cluster to the second cluster.