Third Party Replica Processor Resynchronization Avoidance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing high availability systems for servers face challenges in maintaining data consistency and efficiency during role transfers between active and standby processors, particularly when exceptions occur, leading to time-consuming resynchronization processes that can be voluminous and bandwidth-intensive.
Innovation Solution
A system comprising an active master processor, a standby master processor, and a third party replica processor that maintains logs and uses a negotiation algorithm to determine the latest consistent point, allowing the third party replica to synchronize with the standby master without full resynchronization, thereby avoiding extensive data transfer and maintaining continuous protection.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the third party replica processor performs full resynchronization with the standby master processor during role transfer, then data consistency is ensured, but time consumption and bandwidth usage increase significantly
Solution Approach 1:
The third party replica processor maintains a log of changes locally during normal operation, so that when a role transfer occurs, the replica already has the necessary change information ready. This preliminary accumulation of change logs eliminates the need for full resynchronization and reduces transfer time during failover events.
Solution Approach 2:
The system extracts only the essential change information from the complete data set and transfers only these logged changes during role transfer. By separating the full data set from the change history, the system transfers only the necessary differences, significantly reducing bandwidth consumption and synchronization time while maintaining consistency.
2Reliability
If the third party replica processor maintains continuous monitoring and recording of changes, then data consistency is maintained, but system complexity increases
Solution Approach 1:
The third party replica processor serves multiple functions: it acts as a backup processor, maintains a local log of changes, and can synchronize with either the active master or standby master depending on the situation. This multi-functionality consolidates what would otherwise require separate systems, reducing overall complexity while maintaining reliability.
3Reliability
If the standby master processor takes over execution from the active master processor, then high availability is achieved, but the third party replica may become desynchronized requiring resynchronization
Solution Approach 1:
The system uses feedback from the logged changes to determine the appropriate synchronization strategy. By monitoring which changes have been applied and maintaining an updated log, the system can accurately determine the current state of the standby master relative to the third party replica, enabling precise resynchronization only when necessary rather than performing redundant full synchronizations.
Data Source
AI summary
In a computer system, a standby master processor is configured to serve as a backup processor for an active master processor. A third party replica processor is configured to monitor and record changes on the active master processor when the active master processor is executing, and is further configured to synchronize itself with the standby master processor when the standby master processor takes over execution from the active master processor. Logs of changes are maintained. A negotiation occurs between the standby master processor and the third party replica processor to determine the status of the logs of the standby master processor and the third party replica processor, and logs are applied or paused relating to one or more of the standby master processor and the third party replica processor to synchronize the standby master processor and the third party replica processor.