Initialization protocol for a peer-to-peer replication environment

Patent metadata

Field	Value
Publication number	US-9483541-B2
Application number	US-201213553372-A
Country	US
Kind code	B2
Filing date	Jul 19, 2012
Priority date	Jul 21, 2010
Publication date	Nov 1, 2016
Grant date	Nov 1, 2016

Abstract

Techniques for initializing a connection in a peer-to-peer database replication environment. A message is received from an initiator node, indicating that the initiator node will begin replicating changes made to a particular data entity. One or more replicated changes relating to the database entity are received from the initiator node. If an updated instance of the data entity does not currently exist on a target node then one or more load operations are performed to create the updated instance. The stored replicated changes may then be processed against the updated instance of the database entity.

First claim

What is claimed is:

1. A computer-implemented method for initializing a connection in a peer-to-peer replication environment, comprising:
responsive to a request to add a target node to a data replication group, receiving a first message, at the target node, from an initiator node within the data replication group, indicating that the initiator node will begin replicating changes to the target node without waiting for any acknowledgements relating to the first message, wherein the changes are applied to a first instance of a data entity on the initiator node;
upon receiving the first message indicating that the initiator node will begin replicating changes, transmitting a second message, from the target node, to at least one other member in the data replication group, announcing that the target node is joining the data replication group;
receiving a plurality of replicated changes, at the target node, from at least one member of the data replication group;
determining whether the target node contains a base copy of the data entity, which if updated by application of the plurality of replicated changes would be synchronized with the first instance of the data entity on the initiator node;
upon determining the target node does not contain the base copy of the data entity, performing one or more load operations to create a second instance of the data entity on the target node; and
upon performing the one or more load operations, processing each received replicated change in the plurality of replicated changes against the second instance of the data entity, by operation of one or more computer processors.

2. The computer-implemented method of claim 1 , further comprising:
upon determining that the target node already contains the base copy of the data entity, processing each received replicated change in the plurality of replicated changes against the base copy of the data entity.

3. The computer-implemented method of claim 1 , further comprising:
responsive to transmitting the second message, receiving a second plurality of replicated changes, at the target node, from the other member; and
upon performing the load operations, processing each received replicated change in the second plurality of replicated changes against the second instance of the data entity.

4. The computer-implemented method of claim 1 , wherein the first message specifies that the data entity is a database construct to be synchronized across all the members of the data replication group, and wherein the received replicated changes are associated with the specified database construct.

5. The computer-implemented method of claim 1 , wherein the first message specifies a plurality of data entities to be synchronized between the target node and the initiator node, wherein one of the data entities to be synchronized is a database construct, and wherein the received replicated changes are applied to at least one data entity in the plurality of data entities.

Assignees

• Bourbonnais Serge
• Kulkarni Somil
• Lau Yat O
• IBM

Inventors

• Bourbonnais Serge
• Kulkarni Somil
• Lau Yat O

Classifications

• G06F16/273 Primary

  Asynchronous replication or reconciliation · CPC title

• G06F16/256

  in federated or virtual databases · CPC title

• G06F2201/80

  Database-specific techniques · CPC title

• G06F11/1451

  by selection of backup contents · CPC title

• G06F11/1464

  for networked environments · CPC title