Database Server Synchronization During Switchover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In database systems that perform asynchronous replication, switchover operations often result in delays because synchronization is not completed before client requests can be received, leading to periods where no requests can be processed from the client.
Innovation Solution
A database server with a synchronization processing unit that manages update data and management information in memory, allowing for quick transmission and updating between database servers during role changes, ensuring that update data is synchronized efficiently during switchover operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If asynchronous replication is used to allow the master to receive requests and update the database without waiting for slave synchronization, then the system can continue processing requests during normal operation, but during switchover the slave cannot receive requests until synchronization is completed, causing service interruption
Solution Approach 1:
The slave database server pre-accumulates update data and management information in memory during normal operation. When switchover is triggered, the slave already possesses the necessary data to immediately update its database and begin processing requests, eliminating the synchronization waiting period that previously caused service interruption.
2Reliability
If synchronization is completed before switchover to ensure data consistency, then data integrity is maintained, but the system must stop receiving requests during the synchronization period, reducing availability
Solution Approach 1:
The slave database server independently manages its own data synchronization by pre-accumulating update data and management information in memory. During switchover, the slave performs self-updating using this pre-acquired data without requiring the master to complete full synchronization, thereby maintaining data consistency while preserving service availability.
3Loss of information
If the slave waits for complete synchronization from the master before taking over, then all update data is ensured to be transferred, but the client response time is delayed until synchronization completes
Solution Approach 1:
The slave database server pre-accumulates both update data and management information in memory during the master's operation. When switchover occurs, the slave immediately uses this pre-acquired data to update its database and respond to clients, eliminating the delay that would otherwise occur while waiting for complete synchronization.
Data Source
AI summary
A database server includes a database manager and a synchronization processing unit. When the database server is in a first state in which the database server receives requests from a client, the database manager updates a database in accordance with a request from the client and registers both update data for causing another database server included in the plurality of database servers to update a database of the other database server and management information of the update data for each data management unit in a memory on the basis of the request. When the database server is in the first state, the synchronization processing unit transmits the update data registered in the memory to the other database.