DATABASE MANAGEMENT METHOD, DATABASE SYSTEM AND MEDIUM

• US 20150039558A1
• Filed: 10/17/2014
• Published: 02/05/2015
• Est. Priority Date: 04/18/2012
• Status: Abandoned Application

• Current Assignee: Murakumo Corporation
• Original Assignee: Murakumo Corporation
• Inventors: Yamada, Hiroyuki
• Application Number:
  US14/517,190
• Publication Number:
  US 20150039558A1
• Time in Patent Office: Days
• US Class Current: 707/623
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: G06F 16/245 Query processing
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

From a lower-level master node to a higher-level master node, a shadow copy expanded in its own memory, a heap tuple map, and a shadow index are sent as a write set, and the higher-level master node, upon reception of the write set, verifies whether an update has already been executed and sends a record of this update as a transaction log to the lower-level master node, enabling efficient database updating without a discrepancy, from the lower-level master node to the higher-level master node, as well as from the higher-level master node to the subordinate lower-level master node.

Claims

1. A method of managing a database which hierarchically includes higher-level and lower-level master nodes,

the higher-level and lower-level master nodes each having a database and an index for searching the database,

the method comprising:

when an update instruction for updating the database is issued in any of the lower-level master nodes, generating, by a database processing unit of the lower-level master node, a write set that includes a shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated, and sending the generated write set to a higher-level master node;

comparing, by a database processing unit of the higher-level master node, the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node, and verifying whether a corresponding row of the database that is registered as a target has been updated by a different write set;

aborting, by the database processing unit of the higher-level master node, the write set when the update has been performed, and when the update has not been performed, updating the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index, and generating, by a transaction log processing unit of the higher-level master node, a record of this update as a transaction log;

distributing, by the higher-level master node, the transaction log to the lower-level master nodes including the lower-level master node which has sent the write set; and

updating, by a transaction log processing unit of the lower-level master node, the database of the lower-level master node and the index of the database based on the received transaction log.

2. The method of managing a database according to claim 1, wherein the shadow copy of the write set in the lower-level master node is configured only from newly added rows.

3. The method of managing a database according to claim 1, wherein

the transaction log processing unit of the higher-level master node generates a transaction log that only shows the record of the update associated with the database, and

the transaction log processing unit of the lower-level master node specifies updated contents of the index from the record of the update of the database that is shown by the received transaction log, and updates the index of the lower-level master node based on the specified updated contents.

4. The method of managing a database according to claim 1, wherein

referring, by the database processing unit of the lower-level master node, to the index of the database to extract a corresponding row of the database that is a target of the search processing;

referring to the heap tuple map included in the write set, on a row-by-row basis, to determine whether a row number of the extracted corresponding row is entered or not, including the extracted corresponding row in a search result when the row number is not entered, and removing the extracted corresponding row from the search result when the row number is entered; and

referring to the shadow index included in the write set, extracting an entry of a shadow copy as a target of the search processing, and including the extracted entry in the search result,

are executed, in a stage where the write set is being generated by the lower-level master node, when search processing is executed on the database of the lower-level master node.

5. The method of managing a database according to claim 1, wherein

when the write set is generated in the lower-level master node, an area of a backend memory in the lower-level master node for registering the write set can be referred to at least by the transaction log processing unit of the lower-level master node which executes an update instruction based on the transaction log distributed from the higher-level master node, and

when the transaction log processing unit of the lower-level master node refers to the backend memory and a corresponding row to be updated based on the update instruction is contained in the heap tuple map of the write set, the transaction log processing unit aborts the transaction that is generating this heap tuple map.

6. A method of managing a database of a higher-level master node in a database hierarchically including the higher-level master node and a lower-level master node,

the higher-level and lower-level master nodes each having a database and an index for searching the database,

the method comprising:

receiving a write set which is generated when an update instruction for updating the database is issued in any of the lower-level master nodes and which is generated by a database processing unit of the lower-level master node, the write set including shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated;

comparing, by a database processing unit of the higher-level master node, the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node, and verifying whether a corresponding row of the database that is registered as a target has been updated by a different write set; and

aborting, by the database processing unit of the higher-level master node, the write set when the update has been performed, and when the update has not been performed, updating the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index.

7. The method of managing a database of a higher-level master node according to claim 6, wherein the higher-level master node receives the write set that includes a shadow copy configured only from newly added rows.

8. A method of managing a database of a lower-level master node in a database hierarchically including a higher-level master node and the lower-level master node,

the higher-level and lower-level master nodes each having a database and an index for searching the database,

the method comprising:

when an update instruction for updating the database is issued in any of the lower-level master nodes, generating, by a database processing unit of the lower-level master node, a write set that includes a shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated, and sending the generated write set to a higher-level master node in order to cause the higher-level master node to compare the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node, verify whether a corresponding row of the database that is registered as a target has been updated by a different write set, abort the write set when the update has been performed, and when the update has not been performed, update the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index, generate a record of this update as a transaction log, and distribute the transaction log to the lower-level master nodes including the lower-level master node which has sent the write set; and

updating, by a transaction log processing unit of the lower-level master node upon reception of the transaction log, the database of the lower-level master node and the index of the database based on the received transaction log.

9. The method of managing a database of a lower-level master node according to claim 8, wherein the shadow copy of the write set in the lower-level master node is configured only from newly added rows.

10. The method of managing a database of a lower-level master node according to claim 8, wherein

a transaction log that only shows the record of the update associated with the database is generated in the higher-level master node, and

the transaction log processing unit of the lower-level master node specifies updated contents of the index from the record of the update of the database that is shown by the received transaction log, and updates the index of the lower-level master node based on the specified updated contents.

11. The method of managing a database of a lower-level master node according to claim 8, wherein, in a stage where the write set is being generated by the lower-level master node, when search processing is executed on the database of the lower-level master node, the method executes:

referring, by the database processing unit of the lower-level master node, to the index of the database to extract a corresponding row of the database that is a target of the search processing;

referring to the heap tuple map included in the write set, on a row-by-row basis, to determine whether a row number of the extracted corresponding row is entered or not, including the extracted corresponding row in a search result when the row number is not entered, and removing the extracted corresponding row from the search result when the row number is entered; and

referring to the shadow index included in the write set, extracting an entry of a shadow copy as a target of the search processing, and including the extracted entry in the search result.

12. The method of managing a database of a lower-level master node according to claim 8, wherein

when the write set is generated in the lower-level master node, an area of a backend memory in the lower-level master node for registering the write set can be referred to at least by the transaction log processing unit of the lower-level master node which executes an update instruction based on the transaction log distributed from the higher-level master node, and

when the transaction log processing unit of the lower-level master node refers to the backend memory and a corresponding row to be updated based on the update instruction is contained in the heap tuple map of the write set, the transaction log processing unit aborts the transaction that is generating this heap tuple map.

13. A database system which hierarchically includes higher-level and lower-level master nodes,

the higher-level and lower-level master nodes each having a database and an index for searching the database,

the database system comprising:

a unit for, when an update instruction for updating the database is issued in any of the lower-level master nodes, generating in the lower-level master node where the update instruction is generated a write set that includes a shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated, and sending the generated write set to a higher-level master node;

a unit for, in the higher-level master node, comparing the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node and verifying whether a corresponding row of the database that is registered as a target has been updated by a different write set;

a unit for, in the higher-level master node, aborting the write set when the update has been performed, and when the update has not been performed, updating the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index, and generating a record of this update as a transaction log;

a unit for, in the higher-level master node, distributing the transaction log to the lower-level master nodes including the lower-level master node which has sent the write set; and

a unit for, in the lower-level master node, updating the database of the lower-level master node and the index of the database based on the received transaction log.

14. A computer-readable non-transitory medium on which is recorded a program for causing a higher-level master node of a database hierarchically including the higher-level master node and a lower-level master node which each have a database and an index for searching the database, to execute the steps of:

receiving a write set which is generated when an update instruction for updating the database is issued in any of the lower-level master nodes and which is generated by a database processing unit of the lower-level master node, the write set including shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated;

comparing the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node, and verifying whether a corresponding row of the database that is registered as a target has been updated by a different write set; and

aborting the write set when the update has been performed, and when the update has not been performed, updating the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index.

15. A computer-readable non-transitory medium on which is recorded a program for causing a lower-level master node of a database hierarchically including a higher-level master node and the lower-level master node which each have a database and an index for searching the database, to execute the steps of:

when an update instruction for updating the database is issued in any of the lower-level master nodes, generating a write set that includes a shadow copy expanded in a memory of the lower-level master node and showing updated contents of the database resulted by the update instruction, a heap tuple map showing a row that is a target of the update instruction, and a shadow index showing contents to be added in the index when the database is updated, and sending the generated write set to a higher-level master node in order to cause the higher-level master node to compare the heap tuple map of the write set received from the lower-level master node with the database of the higher-level master node, verify whether a corresponding row of the database that is registered as a target has been updated by a different write set, abort the write set when the update has been performed, and when the update has not been performed, update the database of the higher-level master node and the index of the database by using the shadow copy and the shadow index, generate a record of this update as a transaction log, and distribute the transaction log to the lower-level master nodes including the lower-level master node which has sent the write set; and

updating, upon reception of the transaction log, the database of the lower-level master node and the index of the database based on the received transaction log.