Method and system for replicating data in a cloud storage system

• US 10,445,338 B2
• Filed: 07/23/2013
• Issued: 10/15/2019
• Est. Priority Date: 07/23/2012
• Status: Active Grant

• Current Assignee: NEC Corporation
• Original Assignee: NEC Corporation
• Inventors: Dobre, Dan
• Primary Examiner(s): Trujillo, James
• Assistant Examiner(s): Le, Jessica N
• Application Number:
  US14/416,309
• Publication Number:
  US 20150178364A1
• Time in Patent Office: 2,275 Days
• Field of Search: 707620
• CPC Class Codes: G06F 16/184 implemented as replicated file system
• 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 method for replicating data in a cloud storage system supporting multiple clients, wherein the cloud storage system comprises a plurality of object storing entities (A, B, C) for storing data objects, includes requesting, by a client, values and associated timestamps for a first data object from a first quorum of the object storing entities (A, B, C). The method further includes determining, by the client, a most recent value of the first data object based on the associated timestamps. The method additionally includes performing, by the client, a compare-and-swap procedure, so that the determined value and its corresponding timestamp for the first data object updates the first data object with a value with a newer timestamp and stores the first data object in a second quorum of the object storing entities (A, B, C).

Claims

1. A method for replicating data in a cloud storage system supporting multiple clients, wherein the cloud storage system comprises a plurality of object stores for storing data objects, the method comprising:

requesting, by a client, values and associated timestamps for a data object from a first quorum of the object stores,

determining, by the client, a most recent value of the data object based on the associated timestamps, and

performing, by the client, a compare-and-swap procedure, so that the data object is updated with the most recent value and the data object is stored in a second quorum of the object stores,

wherein the compare-and-swap procedure, for a respective one of the object stores, includes comparing a requested one of the timestamps from the respective one of the object stores with a current timestamp of the respective one of the object stores and updating the data object with the most recent value based on a determination that the requested one of the timestamps from the respective one of the object stores is equal to the current timestamp of the respective one of the object stores.

2. The method according to claim 1, wherein the method further comprises, before the determining the most recent value of the first-data object based on the associated timestamps:

checking whether the data object has a value with a more recent timestamp than the most recent value of the first data object, and

based on the data object having the value with the more recent timestamp, using the value with the more recent timestamp and the corresponding more recent timestamp for performing the compare-and-swap procedure.

3. The method according to claim 1, wherein the compare-and-swap procedure returns the requested one of the timestamps as a result.

4. The method according to claim 1, wherein, based on the data object being modified after the determining the most recent value of the data object and before the performing the compare-and-swap procedure, the compare-and-swap procedure is performed until the data object is not modified anymore between two consecutive performances of the compare-and-swap procedure.

5. The method according to claim 1, wherein during the compare-and-swap procedure, additional responses of object stores not associated with the first quorum are included.

6. The method according to claim 1, wherein, based on the data object being modified after the determining the most recent value of the first-data object and before the performing the compare-and-swap procedure, the compare-and-swap procedure is performed until a quorum of the object stores report values for the data object whose corresponding timestamps are greater than or equal to the timestamp of the determined most recent value of the first data object.

7. The method according to claim 1, wherein the requested one of the timestamps from the respective one of the object stores is an old timestamp and the current one of the timestamps from the respective one of the object stores is a newer timestamp from a compare-and-swap performed by a further client on the respective one of the object stores after the requesting of the values and associated timestamps and before the performing of the compare-and-swap procedure by the client on the respective one of the object stores, the old timestamp and the new timestamp being different from each other such that the compare-and-swap procedure fails and the data object is not updated with the most recent value of the data object.

8. A data replicator in a cloud storage network supporting multiple clients, wherein the cloud storage network comprises a plurality of object stores for storing data objects, the data replicator comprising:

a client configured to;

request values and associated timestamps for a data object from a first quorum of object stores,

determine a most recent value of the data object based on the associated timestamps, and

perform a compare-and-swap procedure, so that the data object is updated with the most recent value and the data object is stored in a second quorum of the object stores,

wherein the compare-and-swap procedure, for a respective one of the object stores, includes comparing a requested one of the timestamps from the respective one of the object stores with a current timestamp of the respective one of the object stores and updating the data object with the most recent value based on a determination that the requested one of the timestamps from the respective one of the object stores is equal to the current timestamp of the respective one of the object stores.