System and method for logical deletion of stored data objects

• US 9,971,706 B2
• Filed: 02/06/2017
• Issued: 05/15/2018
• Est. Priority Date: 09/21/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: McHugh, Jason G., Gattu, Praveen Kumar, Ten-Pow, Michael A., Denny-Brown, II, Derek Ernest
• Primary Examiner(s): Li, Zhuo
• Application Number:
  US15/425,853
• Publication Number:
  US 20170147512A1
• Time in Patent Office: 463 Days
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 12/1466 Key-lock mechanism
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2212/1052 Security improvement
• CPC Class Codes: G06F 3/0608 Saving storage space on storage systems
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0622 in relation to access
• CPC Class Codes: G06F 3/0652 Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0671 In-line storage system
• CPC Class Codes: G06F 3/0673 Single storage device

Abstract

Systems and methods for providing object versioning in a storage system may support the logical deletion of stored objects. In response to a delete operation specifying both a user key and a version identifier, the storage system may permanently delete the specified version of an object having the specified key. In response to a delete operation specifying a user key, but not a version identifier, the storage system may create a delete marker object that does not contain object data, and may generate a new version identifier for the delete marker. The delete marker may be stored as the latest object version of the user key, and may be addressable in the storage system using a composite key comprising the user key and the new version identifier. Subsequent attempts to retrieve the user key without specifying a version identifier may return an error, although the object was not actually deleted.

Claims

1. A system, comprising:

a data store that stores a plurality of objects, wherein at least some of the plurality of objects comprise a same user key and different version identifiers;

one or more processors;

a memory coupled to the one or more processors and storing program instructions that when executed by the one or more processors cause the one or more processors to perform;

receiving a request directed to an object from the data store, wherein the request specifies a user key for the object; and

in response to receiving the request directed to the object;

determining whether the request specifies a particular object version for the object having the specified user key;

in response to determining the request specifies a particular object version identifier for the object, performing the request for the object having the specified user key and the specified particular object version identifier; and

in response to determining the request does not specify a particular object version for the object, performing the request for an object version of the object with the specified user key having a latest object version identifier.

2. The system of claim 1, wherein when executed by the one or more processors, the program instructions further cause the one or more processors to perform:

determining whether the latest object version of the object with the specified user key is a delete marker object; and

in response to determining the latest object version of the object with the specified user key is a delete marker object, refraining from returning object data contained in any of the plurality of objects stored in the data store.

3. The system of claim 2, wherein the delete marker object does not contain object data.

4. The system of claim 1, wherein when executed by the one or more processors, the program instructions further cause the one or more processors to perform, prior to receiving the request directed to the object:

receiving a request to perform a delete operation, wherein the request to perform a delete operation includes the specified user key for the object but does not specify a version identifier; and

in response to receiving the request to perform a delete operation;

generating a new, unique version identifier;

creating a delete marker object, wherein the delete marker object comprises the specified user key for the object and the new, unique version identifier, and wherein the delete marker object becomes the latest object version that is stored in the memory that comprises the specified user key for the object;

refraining from deleting any of the plurality of objects previously stored in the memory in response to receiving the request to perform a delete operation; and

storing the delete marker object in the data store.

5. The system of claim 1, wherein when executed by the one or more processors, the program instructions further cause the one or more processors to perform:

receiving a request to perform a delete operation, wherein the request to perform a delete operation includes the specified user key for the object and a version identifier of a particular version of the object; and

in response to receiving the request to perform a delete operation, deleting the particular version of the object from the data store.

6. The system of claim 1, wherein when executed by the one or more processors, the program instructions further cause the one or more processors to perform:

receiving a request to perform an operation to list user keys of the objects stored in the data store; and

in response to receiving the request to perform an operation to list user keys;

returning a list of user keys contained in object versions stored in the data store, wherein the list does not include user keys contained in delete marker objects that are the latest object versions containing those user keys.

7. The system of claim 1, wherein when executed by the one or more processors, the program instructions further cause the one or more processors to perform:

receiving a request to perform an operation to list all object versions stored in the data store; and

in response to receiving the request to perform an operation to list all object versions;

returning a list of all object versions stored in the data store, wherein the list includes any delete marker objects stored in the data store.

8. A non-transitory, computer-readable storage medium storing program instructions that when executed on one or more computers cause the one or more computers to perform:

receiving a request directed to an object from the data store, wherein the data store stores multiple versions of objects for at least some objects stored in the data store, wherein the request specifies a user key but does not specify a version identifier;

determining an object version of the object having the specified user key with a latest object version identifier; and

performing the request for the object version of the object with the specified user key having the latest object version identifier.

9. The non-transitory, computer-readable storage medium of claim 8, wherein when executed on the one or more computers, the program instructions further cause the one or more computers to perform:

receiving a request for an object from the data store, wherein the request specifies a user key and a version identifier; and

performing the request for a particular version of the object having the specified user key and the specified version identifier.

10. The non-transitory, computer-readable storage medium of claim 8, wherein when executed on the one or more computers, the program instructions further cause the one or more computers to perform:

receiving a request to perform a delete operation, wherein the request to perform a delete operation specifies a user key but does not specify a version identifier; and

in response to receiving the request to perform a delete operation;

generating a new, unique version identifier;

creating a delete marker object, wherein the delete marker object comprises the specified user key and the new, unique version identifier, and wherein the delete marker object becomes the latest object version that is stored in the data store that comprises the specified user key; and

refraining from deleting any of the plurality of objects previously stored in the data store in response to receiving the request to perform a delete operation; and

storing the delete marker object in the data store.

11. The non-transitory, computer-readable storage medium of claim 10, wherein the delete marker object stored in the data store does not contain object data.

12. The non-transitory storage medium of claim 8, wherein when executed on the one or more computers, the program instructions further cause the one or more computers to perform:

receiving a request to perform a delete operation, wherein the request specifies a user key and a version identifier, and wherein the specified user key and version identifier pair identifies a delete marker object; and

in response to receiving the request to perform a delete operation, deleting the delete marker object from the data store.

13. The non-transitory, computer-readable storage medium of claim 8, wherein when executed on the one or more computers, the program instructions further cause the one or more computers to perform:

suspending an object versioning feature for the data store;

receiving a request to perform a delete operation, wherein the request specifies a user key, but does not specify a version identifier; and

in response to receiving the request to perform a delete operation;

creating a new delete marker object comprising a special, sentinel version identifier and the specified user key; and

storing the new delete marker object in the data store;

wherein creating the new delete marker comprises;

deleting object data contained in an object previously stored in the data store and comprising the specified user key and the special sentinel version identifier; and

marking the object previously stored in the data store and comprising the specified user key and the special sentinel version identifier as a delete marker object.

14. A method, comprising:

receiving a request directed to an object from a data store, wherein the data store stores multiple versions of objects for at least some objects stored in the data store, wherein the request specifies a user key for the object, but does not specify a version identifier;

determining an object version of the object having the specified user key with a latest object version identifier; and

performing the request for an object version of the object with the specified user key having the latest object version identifier.

15. The method of claim 14, further comprising:

receiving a request directed to an object from the data store, wherein the request specifies a user key for the object and a particular version identifier, wherein the version identifier is not a version identifier for the latest version of the object; and

performing the request for an object version of the object with the specified user key having the specified object version identifier.

16. The method of claim 14, further comprising:

receiving a request directed to an object from the data store, wherein the request specifies a user key for the object, but does not specify a version identifier;

determining an object version of the object having the specified user key with a latest object version identifier, wherein the latest object version identifier is a delete marker object; and

refraining from returning object data contained in any of the plurality of objects stored in the data store.

17. The method of claim 14, further comprising:

receiving a request directed to an object from the data store, wherein the request specifies a user key for the object and a particular version identifier, wherein the version identifier is not a version identifier for the latest version of the object, and wherein the version identifier is a delete marker object; and

returning an error indication.

18. The method of claim 14, further comprising:

receiving a request to delete an object from the data store, wherein the request specifies a user key for the object and a particular version identifier, wherein the version identifier is not a version identifier for the latest version of the object, and wherein the version identifier is a delete marker object; and

deleting the delete marker object from the data store.

19. The method of claim 14, further comprising:

suspending an object versioning feature for the data store;

receiving a request to perform a delete operation, wherein the request specifies a user key, but does not specify a version identifier; and

in response to receiving the request to perform a delete operation;

creating a new delete marker object comprising a special, sentinel version identifier and the specified user key; and

storing the new delete marker object in the data store;

wherein creating the new delete marker comprises;

deleting object data contained in an object previously stored in the data store and comprising the specified user key and the special sentinel version identifier; and

marking the object previously stored in the data store and comprising the specified user key and the special sentinel version identifier as a delete marker object.

20. The method of claim 14, further comprising:

receiving a request to perform a delete operation, wherein the request to perform a delete operation specifies a user key but does not specify a version identifier; and

in response to receiving the request to perform a delete operation;

generating a new, unique version identifier;

creating a delete marker object, wherein the delete marker object comprises the specified user key and the new, unique version identifier, and wherein the delete marker object becomes the latest object version that is stored in the data store that comprises the specified user key; and

refraining from deleting any of the plurality of objects previously stored in the data store in response to receiving the request to perform a delete operation; and

storing the delete marker object in the data store.

21. The method of claim 20, wherein the delete marker object stored in the data store does not contain object data.