IP Library › Granted Patent US 8,423,507
Granted Patent B2
US 8,423,507 · App. 13/257,070 · Granted Apr 16, 2013

Method and system for managing replication of data

Inventor: Hiroyuki Yamada (Tokyo, JP)
Assignee: Murakumo Corporation
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,423,507
App. No.
13/257,070
Granted
Apr 16, 2013
Kind
B2
Abstract

Data replication management which enables rapid retrieval while increasing the performance of the entire system, and maintaining data synchronization regarding successively updated data is performed. There are steps which comprises a step that when a slave node which has received an instruction for retrieval does not receive a return massage from a master node within a predetermined time period (Ts1) from the transmission of a request message to the master node, the slave node requests the master node to provide a transaction log up to the latest version with respect to the update of a master database; a step that the master node which has received the request transmits the transaction log to the slave node; and a step that the slave node updates a replica database with reference to the transaction log transferred from the master node.

Claims (16)

1. A method for managing replication of data between a master database managed by a master node and replica databases managed by a plurality of slave nodes connected to a tree structure having the master node as a root in a manner of having contents identical with that of the master database and which are used as search targets, the method comprising:

the slave node, which has received a search instruction to search the data, transmitting to a parent node of the slave node a request for a transaction log up to the latest version related to an update of the master database, in a case of not receiving a reply message in a heart beat communication from the parent node within a predetermined time (Ts3) from the time of transmission of a request message in the heart beat communication to the parent node of the slave node;

when the parent node which has received the request does not have the transaction log, the parent node which has received the request makes a request to its parent node for the transaction log, wherein the request is repeated to further parent nodes higher in the tree structure until a parent node having the transaction log is reached;

the parent node, which has received the request and has the transaction log, transmits the transaction log to its child nodes, wherein the transmitting is repeated from each node to its child nodes until the slave node which has received the search instruction receives the transaction log; and

the slave node updating the replica database by referring to the received transaction log.

2. The method for managing replication of data according to claim 1 , further comprising the slave node updating the replica database by referring to the already received transaction log, in a case of receiving a reply message in the heart beat communication from the parent node within the predetermined time (T s3 ) from the time of transmission of a request message in the heart beat communication to the parent node of the slave node.

3. The method for managing replication of data according to claim 1 or 2 , further comprising the node in the tree structure having the transaction log transmitting, after transmission to the child node the transaction log up to the latest version related to updates of the master database and upon receipt of a notification of completion of transfer from each of all child nodes from which the node have received a new request message within the predetermined time (T r3 ) from the time of receiving the request message, a notification of completion of transfer to its parent node.

4. The method for managing replication of data according to claim 1 or 2 , further comprising the node, which does not have the transaction log up to the latest version related to updates of the master database and when it has received requests for the transaction log from any of the child nodes of the node, requesting for the transaction log to the parent node of the node, by collecting the requests from the child nodes.

5. The method for managing replication of data according to claim 3 , further comprising the node, which does not have the transaction log up to the latest version related to updates of the master database and when it has received requests for the transaction log from any of the child nodes of the node, requesting for the transaction log to the parent node of the node, by collecting the requests from the child nodes.

6. A system for managing replication of data between a master database managed by a master node and replica databases managed by a plurality of slave nodes connected to a tree structure having the master node as a root in a manner of having contents identical with that of the master database and which are used as search targets, the system comprising:

means for transmitting, from the slave node which has received a search instruction to search the data, to a parent node of the slave node, a request for a transaction log up to the latest version related to an update of the master database, in a case of not receiving a reply message in a heart beat communication from the parent node within a predetermined time (Ts3) from the time of transmission of a request message in the heart beat communication to the parent node of the slave node;

means for making a request for the transaction log, from the parent node which has received the request and does not have the transaction log, to its parent node, wherein the request is repeated to further parent nodes higher in the tree structure until a parent node having the transaction log is reached;

means for transmitting the transaction log, from the parent node which has received the request and has the transaction log, to its child nodes, wherein the transmitting is repeated from each node to its child until the slave node which has received the search instruction receives the transaction log; and

means for updating the replica database of the slave node by referring to the received transaction log.

7. The system of managing replication of data according to claim 6 , further comprising:

means for causing the slave node to update the replica database by referring to the transaction log, which has been already received, according to the search instruction, when a reply message has been received from the parent node within the predetermined time (T s3 ) from the time of transmission of the request message to the parent node of the slave node.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 19, 2011
From: YAMADA, HIROYUKI
To: MURAKUMO CORPORATION
Reel/Frame 026925/0056 →
Priority Claims (1)
JP 2009-069140 · Mar 19, 2009 · national
Continuity (1)
Related Publication 20120011098A1 · Jan 12, 2012