DATABASE MANAGEMENT SYSTEM FOR PROVIDING PARTIAL RE-SYNCHRONIZATION AND PARTIAL RE-SYNCHRONIZATION METHOD OF USING THE SAME

• US 20150347250A1
• Filed: 01/29/2015
• Published: 12/03/2015
• Est. Priority Date: 05/30/2014
• Status: Abandoned Application

• Current Assignee: Altibase Corp.
• Original Assignee: Altibase Corp.
• Inventors: Kim, Jun Young, Lee, Seung Won, Kim, Jung Keun, Yu, Jeong Seung
• Application Number:
  US14/609,097
• Publication Number:
  US 20150347250A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

Provided is a database management system (DBMS). The DBMS synchronizes an active node with a standby node and detects a point of time when last synchronization is performed between the active node and the standby node. Then, after the DBMS performs page synchronization from the detected point of time of the last synchronization to a point at which a failover occurs in the active node, the DBMS performs partial log synchronization by receiving a log from the standby node after the point of time of the last synchronization until the active node is recovered.

Claims

1. A database management system (DBMS) for providing partial re-synchronization, the DBMS comprising:

a log synchronization unit for asynchronously transmitting a log from a first node to a second node and performing a redo operation internally on a log received by the second node;

a partial page synchronization unit for checking which data pages in the first node are affected due to log operations performed on a GAP part of the first node and receiving corresponding data pages from the second node and overwriting the affected data pages in the first node with the corresponding data pages of the second node; and

a log re-synchronization unit, which is operated in the first node after a failed first node restarts, for comparing a sequence number of newly updated transaction log data in the second node to a sequence number of applying data pages in the first node and receiving the newly updated transaction log data whose update sequence number is greater than the sequence number of the applying data pages in the first node, wherein the first node acting as a master server is actively used to run the DBMS, while the second node acting as a slave server is in a standby node ready to take over if a failover occurs, and when the failed master server restarts, the first node performs partial page synchronization and log re-synchronization,

wherein the GAP part represents a section from right after a point at which synchronization is performed last between the first node and the second node before a failover occurs in the first node to a point at which a log is recorded last in the first node before the failover occurs.

2. The DBMS of claim 1, wherein the partial page synchronization unit determines that the data pages in the first node are affected only when the log operations performed on the GAP part of the first node make an alteration to any of the data pages.

3. The DBMS of claim 1, wherein the partial page synchronization unit determines that the data pages in the first node are unaffected when the log operations performed on the GAP part of the first node make no alteration to any of the data pages.

4. A database management system (DBMS) for providing partial re-synchronization, the DBMS comprising:

a log synchronization unit for asynchronously transmitting a log from an active node to a standby node;

a search unit for searching for a point at which synchronization is performed last between the active node and the standby node if a failover occurs in the active node;

a log checking unit for checking whether at least a log, which is recorded after the point at which the synchronization is performed last in the active node, is present in the active node when the failover occurs;

a partial page synchronization unit for checking which data pages in the active node are affected due to a log operation performed on the log that is checked by the log checking unit and overwriting the affected data pages in the active node with corresponding data pages in the standby node after the failed active node restarts; and

a log re-synchronization unit, which is operated in the active node after the failed active node restarts, for comparing a sequence number of newly updated transaction log data in the standby node to a sequence number of applying data pages in the active node and receiving the newly updated transaction log data whose sequence number is greater than the sequence number of the applying data pages in the active node.

5. The DBMS of claim 4, wherein the active node acting as a master server is actively used to run the DBMS, while the standby node acting as a slave server is in the standby node ready to take over if a failover occurs, and when the failed active node restarts, the active node performs log re-synchronization in the log re-synchronization unit.

6. The DBMS of claim 4, wherein the partial page synchronization unit determines that the data pages in the first node are affected only when the log operations performed on the log that is checked by the log checking unit make an alteration to any of the data pages.

7. The DBMS of claim 4, wherein the active node acting as a master server is actively used to run the DBMS, while the standby node acting as a slave server is ready to take over if a failure occurs,

wherein the partial page synchronization unit overwrites the affected data pages in the active node with the corresponding data pages in the standby node after the failed active node restarts.

8. The DBMS of claim 4, wherein the active node is a master server for performing a DBMS management service until before a point of time when the failover occurs, and is a server for processing a requirement of a client.

9. The DBMS of claim 4, wherein the standby node is a server for obtaining backup of data of the active node via communication with the active node and ensures availability by performing a transaction service in the standby node if a failover occurs in the active node.

11. The DBMS of claim 9, wherein the partial page synchronization unit determines that the data pages in the active node are affected only when the log operations performed on the GAP part of the active node make an alteration to any of the data pages.

10. A database management system (DBMS) for providing partial re-synchronization, the DBMS comprising:

an active node for communicating with a client and processing a requirement of the client;

a standby node for asynchronously obtaining backup of data of the active node via communication with the active node and performing a transaction service instead of the active node if a failover occurs in the active node;

a log synchronization unit that is implemented in a standby node and performs a redo operation by asynchronously receiving a log from the active node;

a partial page synchronizing unit that is implemented in the active node and overwrites data pages affected by log operations committed during a GAP part with corresponding data pages from the standby node ; and

a log re-synchronization unit, which is operated in the active node after a failed active node restarts, for comparing a sequence number of newly updated transaction log data in the standby node to a sequence number of applying data pages in the active node and receiving, in the active node, the newly updated transaction log data whose update sequence number is greater than the sequence number of the applying data pages.

wherein the active node acting as a master server is actively used to run the DBMS, while the standby node acting as a slave server is ready to take over if a failure occurs, and the partial page synchronizing unit and the log re-synchronization unit are configured to operate after the failed active node restarts.

12. A method of partially synchronizing a log, which is performed by a database management system (DBMS), the method comprising:

asynchronously transmitting a log from an active node to a standby node and performing a redo operation internally on a log received by the second node, which is performed by a log synchronization unit;

checking whether at least a log, which is recorded after a point at which the synchronization is performed last in the active node, is present when a failover occurs;

replacing data pages affected by log operations done to the at least a log in the active node with corresponding data pages from the standby node;

comparing a sequence number of newly updated transaction log data in the standby node to a sequence number of applying data pages in the active node, which is performed by a log re-synchronization unit, wherein the log re-synchronization unit is operated in the active node after the failed active node restarts; and

receiving, in the active node, the newly updated transaction log data whose sequence number is greater than the sequence number of the applying data pages.