Reconciliation in sync replication

• US 10,452,489 B2
• Filed: 07/24/2017
• Issued: 10/22/2019
• Est. Priority Date: 08/29/2014
• Status: Active Grant

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Mu, Yuedong, Sundararajan, Manoj V., Ngan, Ching-Yuk Paul
• Primary Examiner(s): Patel, Kamini B
• Application Number:
  US15/658,112
• Publication Number:
  US 20170329678A1
• Time in Patent Office: 820 Days
• Field of Search: 714 632, 714 623
• CPC Class Codes: G06F 11/00 Error detection; Error correction; Monitoring error detection, correction or monitoring in information storage based on relative movement between record carrier and transducer G11B20/18; monitoring, i.e. supervising the progress of recording or reproducing G11B27/36; in static stores G11C29/00
• CPC Class Codes: G06F 11/0751 Error or fault detection not based on redundancy power supply failures G06F1/30; network fault management H04L41/06
• CPC Class Codes: G06F 11/0766 Error or fault reporting or storing
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1658 Data re-synchronization of a redundant component, or initial sync of replacement, additional or spare unit
• CPC Class Codes: G06F 11/2058 using more than 2 mirrored copies
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2076 Synchronous techniques
• CPC Class Codes: G06F 11/2089 Redundant storage control functionality
• CPC Class Codes: G06F 11/3034 where the computing system component is a storage system, e.g. DASD based or network based digital input from or digital output to record carriers G06F3/06; digital recording or reproducing G11B20/18; for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS], H04L67/1097
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A distributed storage system replicates data for a primary logical storage object on a primary node of the storage system to a secondary logical storage object on a secondary node on the distributed storage system. Failures in writing data to the primary logical storage object or failures in the replication of the data to the secondary logical storage object can cause data that should be synchronized to become divergent. In cases where the data may be divergent, reconciliation operations can be performed to resynchronize the data.

Claims

1. A method comprising:

replicating a first request, received by a first node to write data to a first storage unit, to a second node as a replicated first request that causes the second node to perform a second write operation to write the data to a second storage unit;

performing a first abort operation on the first node based upon a second request to abort the first request;

forwarding the second request to the second node to invoke the second node to perform a second abort operation; and

performing a reconciliation operation based upon results of the first abort operation and the second abort operation.

2. The method of claim 1, comprising:

performing a reconciliation to synchronize data at the first storage unit and data at the second storage unit.

3. The method of claim 1, wherein old data overwrites data, stored on the second storage unit, based upon the reconciliation operation.

4. The method of claim 1, comprising:

terminating data replication between the first node and the second node based upon the second write operation failing to write the data to the second storage unit.

5. The method of claim 1, comprising:

performing a reconciliation to write old data from the first storage unit to the second node for overwriting new data at the second storage unit based upon the first request failing to write the new data to the first storage unit.

6. The method of claim 1, comprising:

forwarding first data from the first storage unit to the second node to invoke the second node to overwrite second data on the second storage unit with the first data based upon a determination that the first abort operation failed and the second abort operation succeeded.

7. The method of claim 1, comprising:

forwarding first data from the first storage unit to the second node to invoke the second node to overwrite second data on the second storage unit with the first data based upon a determination that the first abort operation succeeded and the second abort operation failed.

8. A non-transitory machine readable medium having stored thereon program code which when executed by a machine, causes the machine to:

replicate a first request, received by a first node to write data to a first storage unit, to a second node as a replicated first request that causes the second node to perform a second write operation to write the data to a second storage unit;

perform a first abort operation on the first node based upon a second request to abort the first request;

forward the second request to the second node to invoke the second node to perform a second abort operation; and

perform a reconciliation operation based upon results of the first abort operation and the second abort operation.

9. The non-transitory machine readable medium of claim 8, wherein the program code causes the machine to:

read, by the first node, old data from a location targeted by the first request and forward the old data to the second node based upon a determination that the first request failed to write the data to the first storage unit.

10. The non-transitory machine readable medium of claim 9, wherein the program code causes the machine to:

instruct the second node to write the old data, wherein the old data overwrites data stored on the second storage unit.

11. The non-transitory machine readable medium of claim 8, wherein the program code causes the machine to:

terminate data replication between the first node and the second node.

12. The non-transitory machine readable medium of claim 8, wherein the first request is to write the data for a first logical storage object at the first storage unit and the second write operation is to write the data for a second logical storage object at the second storage unit.

13. The non-transitory machine readable medium of claim 8, wherein the program code causes the machine to:

forward first data from the first storage unit to the second node to invoke the second node to overwrite second data on the second storage unit with the first data based upon a determination that the first abort operation failed and the second abort operation succeeded.

14. The non-transitory machine readable medium of claim 8, wherein the program code causes the machine to:

forward first data from the first storage unit to the second node to invoke the second node to overwrite second data on the second storage unit with the first data based upon a determination that the first abort operation succeeded and the second abort operation failed.

15. A device comprising:

a memory having stored program code; and

a processor coupled to the memory, the processor configured to execute the program code to cause the processor to;

replicate a first request, received by a first node to write data to a first storage unit, to a second node as a replicated first request that causes the second node to perform a second write operation to write the data to a second storage unit;

perform a first abort operation on the first node based upon a second request to abort the first request;

forward the second request to the second node to invoke the second node to perform a second abort operation; and

perform a reconciliation operation based upon results of the first abort operation and the second abort operation.

16. The device of claim 15, wherein the program code causes the processor to:

perform a reconciliation to synchronize data at the first storage unit and data at the second storage unit.

17. The device of claim 15, wherein the program code causes the processor to:

instruct the second node to write old data, wherein the old data overwrites the data stored on the second storage unit.

18. The device of claim 15, wherein the program code causes the processor to:

terminate data replication between the first node and the second node.

19. The device of claim 15, wherein the program code causes the processor to:

perform a reconciliation to write old data from the first storage unit to the second node for overwriting new data at the second storage unit based upon the first request failing to write the new data to the first storage unit.

20. The device of claim 15, wherein the program code causes the processor to:

forward first data from the first storage unit to the second node to invoke the second node to overwrite second data on the second storage unit with the first data based upon a determination that the first abort operation failed and the second abort operation succeeded.