RECORDING MEDIUM, NODE, AND DISTRIBUTED DATABASE SYSTEM

• US 20130085988A1
• Filed: 09/13/2012
• Published: 04/04/2013
• Est. Priority Date: 09/29/2011
• Status: Abandoned Application

• Current Assignee: Fujitsu Limited
• Original Assignee: Fujitsu Limited
• Inventors: HIRAGUCHI, Tomohiko, Takebe, Nobuyuki
• Application Number:
  US13/614,632
• Publication Number:
  US 20130085988A1
• Time in Patent Office: Days
• US Class Current: 707/609
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• 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

A non-transitory computer-readable recording medium for recording a data management program to cause a computer to execute a process, the process comprising, within a prescribed time period after a record stored in another computer is updated, storing the updated record so that the record before the updating and the updated record are stored in a storage unit, and by a point in time at which the prescribed time period has passed from a second point in time that is a point in time from which the prescribed time period has passed from a first point in time, receiving a reference request for the updated record, and when a transaction to perform the updating in the another computer is present at the first point in time, transmitting the record before the updating that is stored in the storage unit to a requestor of the reference request.

Claims

1. A non-transitory computer-readable recording medium for recording a data management program to cause a computer to execute a process, the process comprising:

within a prescribed time period after a record stored in another computer is updated, storing the updated record so that the record before the updating and the updated record are stored in a storage unit; and

by a point in time at which the prescribed time period has passed starting from a second point in time that is a point in time from which the prescribed time period has passed starting from a first point in time, receiving a reference request for the record, and when a transaction to perform the updating in the another computer is present at the first point in time, transmitting the record before the updating that is stored in the storage unit to a requestor of the reference request.

2. The recording medium of claim 1, wherein the process further comprises receiving the reference request, and when the transaction to perform the updating is not present at the first point in time, transmitting the updated record stored in the storage unit to the requestor of the reference request.

3. A node comprising:

a cache to store cache data that is at least a portion of data stored in another node, a first transaction list indicating a list of transactions executed in a distributed database system, and a first point in time indicating a point in time at which a request for the first transaction list is received by a transaction manager device; and

a processor, when a reference request of records of a plurality of generations included in the cache data is received, to receive and to store in the cache a second transaction list and a second point in time indicating a point in time at which the transaction manager device received a request for the second transaction list, to compare the first point in time with the second point in time, to select either the first transaction list or the second transaction list as a third transaction list by using a result of the comparing, and to identify a record of a generation to be referred to from among the records of the plurality of generations by using the third transaction list.

4. The node of claim 3 wherein

the node periodically receives the first transaction list and the first point in time from the transaction manager device.

5. The node of claim 3 wherein

the node determines whether or not data stored in the another node corresponding to the cache data is updated, and deletes the cache data when the data is updated.

6. The node of claim 5 wherein

the node receives a fourth transaction list and a fourth point in time indicating a point in time at which a transaction manager device received a request from the fourth transaction list before the processing of determining whether or not the data stored in the another node corresponding to the cache data has been updated, and stores in the cache the fourth transaction list and the fourth point in time as the first transaction list and the first point in time, respectively, after termination of the determining processing.

7. A distributed database system comprising:

a transaction manager device including;

a first processor to manage a transaction list indicating a list of transactions in execution in the distributed database system, and to transmit to a node a point in time at which a request from the node is received; and

a plurality of nodes, wherein each of the plurality of nodes includes;

a cache to store cache data that is at least a portion of data stored in another node, a first transaction list indicating a list of transactions executed in a distributed database system, and a first point in time indicating a point in time at which a request for the first transaction list is received by a transaction manager device; and

a second processor, when a reference request of records of a plurality of generations included in the cache data is received, to receive and to store in the cache a second transaction list and a second point in time indicating a point in time at which the transaction manager device received a request for the second transaction list, to compare the first point in time with the second point in time, to select either the first transaction list or the second transaction list as a third transaction list by using a result of the comparing, and to identify a record of a generation to be referred to from among the records of the plurality of generations by using the third transaction list.