Initialization protocol for a peer-to-peer replication environment

Patent metadata

Field	Value
Publication number	US-10255343-B2
Application number	US-201615299314-A
Country	US
Kind code	B2
Filing date	Oct 20, 2016
Priority date	Jul 21, 2010
Publication date	Apr 9, 2019
Grant date	Apr 9, 2019

Abstract

Techniques for initializing a connection in a peer-to-peer replication environment. Responsive to a request to add a target node to a data replication group, embodiments receive a first message, at a 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. The changes are applied to a first instance of a data entity on the initiator node. A second message is transmitted, 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. Embodiments receive a plurality of replicated changes, at the target node, from the initiator node, and process each replicated change in the plurality of replicated changes against a second instance of the data entity at the target node.

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 a 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 the initiator node; and
processing each received replicated change in the plurality of replicated changes against a second instance of the data entity at the target node.

2. The computer-implemented method of claim 1 , further comprising:
upon determining that the target node already contains a 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 , wherein the target node and the initiator node are members of a data replication group.

4. 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 a plurality of load operations, processing each received replicated change in the second plurality of replicated changes against the second instance of the data entity.

5. 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 members of the data replication group, and wherein the received replicated changes are associated with the database construct.

6. 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.

7. A system, comprising:
one or more computer processors; and
a memory containing computer program code that, when executed by operation of the one or more computer processors, performs an operation for initializing a connection in a peer-to-peer replication environment, the operation comprising:
responsive to a request to add a target node to a data replication group, receiving a first message, at a 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 the initiator node; and
processing each received replicated change in the plurality of replicated changes against a second instance of the data entity at the target node.

8. The system of claim 7 , the operation further comprising:
upon determining that the target node already contains a 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.

9. The system of claim 7 , wherein the target node and the initiator node are members of a data replication group.

10. The system of claim 7 , the operation 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 a plurality of load operations, processing each received replicated change in the second plurality of replicated changes against the second instance of the data entity.

11. The system of claim 7 , wherein the first message specifies that the data entity is a database construct to be synchronized across all members of the data replication group, and wherein the received replicated changes are associated with the database construct.

12. The system of claim 7 , 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.

13. A computer-readable storage medium containing computer program code that, when executed by operation of one or more computer processors, performs an operation for initializing a connection in a peer-to-peer replication environment, the operation comprising:
responsive to a request to add a target node to a data replication group, receiving a first message, at a 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 the initiator node; and
processing each received replicated change in the plurality of replicated changes against a second instance of the data entity at the target node.

14. The computer-readable storage medium of claim 13 , the operation further comprising:
upon determining that the target node already contains a 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.

15. The computer-readable storage medium of claim 13 , wherein the target node and the initiator node are members of a data replication group.

16. The computer-readable storage medium of claim 13 , the operation 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 a plurality of load operations, processing each received replicated change in the second plurality of replicated changes against the second instance of the data entity.

17. The computer-readable storage medium of claim 13 , wherein the first message specifies that the data entity is a database construct to be synchronized across all members of the data replication group, and wherein the received replicated changes are associated with the database construct.

Assignees

• IBM

Inventors

• Bourbonnais Serge
• Kulkarni Somil
• Lau Yat O

Classifications

• G06F11/1464

  for networked environments · CPC title

• 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