Versioning schemes for compute-centric object stores

• US 9,092,238 B2
• Filed: 03/15/2013
• Issued: 07/28/2015
• Est. Priority Date: 03/15/2013
• Status: Active Grant

• Current Assignee: Joyent, Inc. (Samsung Electronics Co. Ltd.)
• Original Assignee: Joyent, Inc. (Samsung Electronics Co. Ltd.)
• Inventors: Cavage, Mark, Pacheco, David, Cantrill, Bryan, Fitch, Nathan
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US13/838,150
• Publication Number:
  US 20140282615A1
• Time in Patent Office: 865 Days
• Field of Search: 719/310, 707/813
• US Class Current: 1/1
• 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
• CPC Class Codes: G06F 9/4493 Object persistence
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

Versioning schemes for compute-centric object stores are provided herein. An exemplary method may include creating a metadata clone of a first object within an object store via a versioning scheme module, the metadata of the first object being stored in the object store on a first path, establishing a copy on write link between the first path and a second path for the first object via the versioning scheme module, and storing the cloned metadata on the second path via the versioning scheme module.

Claims

1. A method, comprising:

creating a metadata clone of a first object within an object store via a versioning scheme module, the metadata of the first object being stored in the object store on a first path;

executing a cleanup task by a cleanup agent, the cleanup agent walking activity records for an object in chronological order to determine one or more deleteable versions of the object;

establishing a copy on write link between the first path and a second path for the first object via the versioning scheme module; and

storing the cloned metadata on the second path via the versioning scheme module.

2. The method according to claim 1, further comprising storing a second object in the object store on the first path via the versioning scheme module, the second object comprising an update of the first object.

3. The method according to claim 2, further comprising:

receiving a request for the first path; and

returning the second object.

4. The method according to claim 1, further comprising:

receiving a request for the second path; and

returning the first object from the second path.

5. The method according to claim 1, wherein the metadata comprises any of a user identifier, a storage server identifier that indicates a name and a location of physical storage node that stores the object, an object identifier, and a key that indicates a path for the object on the storage server.

6. The method according to claim 1, wherein a deleteable version of an object comprises an object version having an age that is greater than a grace period established for the object store.

7. The method according to claim 1, wherein a deleteable version of an object is determined by the cleanup agent comparing a number of versions of an object in an object record to a threshold value that defines a largest number of versions of an object which can be stored on the object store at the same time.

8. A system, comprising:

one or more processors; and

logic encoded in one or more tangible media for execution by the one or more processors, the logic comprising;

a versioning scheme module that creates a metadata clone of a first object within an object store, the metadata of the first object being stored in the object store on a first path;

the versioning scheme module establishing a copy on write link between the first path and a second path for the first object;

the versioning scheme module storing the cloned metadata on the second path; and

a cleanup agent that executes a cleanup task, the cleanup agent configured to walk records for an object in chronological order to determine one or more deleteable versions of the object.

9. The system according to claim 8, wherein the versioning scheme module is configured to store a second object in the object store on the first path, the second object comprising an update of the first object.

10. The system according to claim 9, further comprising a network service that:

receives a request for the first path; and

returns the second object.

11. The system according to claim 8, further comprising network service that:

receives a request for the second path; and

returns the first object from the second path.

12. The system according to claim 8, wherein the metadata comprises any of a user identifier, a storage server identifier that indicates a name and a location of physical storage node that stores an object identifier, and a key that indicates a path for the object on the storage server.

13. The system according to claim 8, wherein a deleteable version of an object comprises an object version having an age that is greater than a grace period established for the object store.

14. The system according to claim 8, wherein a deleteable version of an object is determined by the cleanup agent comparing a number of versions of an object in an object record to a threshold value that defines a largest number of versions of an object which can be stored on the object store at the same time.

15. A method, comprising:

creating a metadata clone of a first object within an object store via a versioning scheme module, the metadata of the first object being stored in the object store on a first path;

executing a cleanup task by a cleanup agent, the cleanup agent walking activity records for an object in chronological order to determine one or more deleteable versions of the object;

establishing a copy on write link between the first path and a second path for the first object via the versioning scheme module;

storing the cloned metadata on the second path via the versioning scheme module; and

writing an update of the first object to a third path, wherein the first object remains linked to the second path such that requests for the first object result in a return of the second path while requests for the updated object result in a return of the third path.