US2015331902A1PendingUtilityA1

Distributed Storage Object Delete

Assignee: FUTUREWEI TECHNOLOGIES INCPriority: Jan 31, 2013Filed: Jul 28, 2015Published: Nov 19, 2015
Est. expiryJan 31, 2033(~6.5 yrs left)· nominal 20-yr term from priority
G06F 17/30197G06F 17/30117G06F 17/30371G06F 17/30607G06F 16/162G06F 16/183G06F 16/2365G06F 16/1824G06F 16/289
44
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

System and methods for storage object distribution using dynamic policy controls are provided. An embodiment method deleting an object in a distributed storage system includes receiving, from a client, a delete request for an object, retrieving, by a primary datacenter, an object metadata list corresponding to the object to be deleted, and inserting, by the primary datacenter, a delete marker on a top of a stack data structure in an object metadata list.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method of updating metadata in a distributed storage system, the method comprising:
 storing one or more versions of an object in a memory of a secondary datacenter, wherein each of the one or more versions of the object are associated with a different entity tag;   receiving, by the secondary datacenter, a delete request from a primary datacenter, wherein the delete request requests that the secondary datacenter delete portions of a specific version of the object stored by the secondary datacenter;   deleting at least a portion of a first version of the object from the memory of the second datacenter when a first entity tag associated with the first version of the object matches an entity tag carried by the delete request; and   sending, by the secondary datacenter, a delete response to the primary datacenter.   
     
     
         2 . The method of  claim 1 , wherein the delete response carries the first entity tag when the first entity tag matches the entity tag carried by the delete request. 
     
     
         3 . The method of  claim 2 , wherein the delete response indicates, to the primary datacenter, a successfully deletion of the portion of the first version of the object when the delete response carries the first entity tag. 
     
     
         4 . The method of  claim 1 , wherein deleting at least the portion of the first version of the object comprises deleting the entire first version of the object from the memory of the secondary datacenter. 
     
     
         5 . The method of  claim 1 , wherein deleting at least the portion of the first version of the object comprises deleting a first sub-portion of the first version of the object from the memory of the secondary datacenter, wherein a second sub-portion of the first version of the object remains stored in the memory of the secondary datacenter. 
     
     
         6 . The method of  claim 1 , wherein the delete response indicates, to the primary datacenter, that the portion of the specific version of the object was not successfully deleted when the delete response does not carry an entity tag. 
     
     
         7 . A secondary datacenter comprising:
 a processor; and   a non-transitory computer readable storage medium storing programming for execution by the processor, the programming including instructions to:
 store one or more versions of an object in a memory of a secondary datacenter, wherein each of the one or more versions of the object are associated with a different entity tag; 
 receive a delete request from a primary datacenter, wherein the delete request requests that the secondary datacenter delete portions of a specific version of the object stored by the secondary datacenter; 
 delete at least a portion of a first version of the object from the memory of the second datacenter when a first entity tag associated with the first version of the object matches an entity tag carried by the delete request; and 
   send a delete response to the primary datacenter.   
     
     
         8 . The secondary datacenter of  claim 7 , wherein the delete response carries the first entity tag when the first entity tag matches the entity tag carried by the delete request. 
     
     
         9 . The secondary datacenter of  claim 8 , wherein the delete response indicates, to the primary datacenter, a successfully deletion of the portion of the first version of the object when the delete response carries the first entity tag. 
     
     
         10 . The secondary datacenter of  claim 7 , wherein the instructions to delete at least the portion of the first version of the object include instructions to delete the entire first version of the object from the memory of the secondary datacenter. 
     
     
         11 . The secondary datacenter of  claim 7 , wherein the instructions to delete at least the portion of the first version of the object include instructions to delete a first sub-portion of the first version of the object from the memory of the secondary datacenter, wherein a second sub-portion of the first version of the object remains stored in the memory of the secondary datacenter. 
     
     
         12 . The secondary datacenter of  claim 7 , wherein the delete response indicates, to the primary datacenter, that the portion of the specific version of the object was not successfully deleted when the delete response does not carry an entity tag. 
     
     
         13 . A method of updating metadata in a distributed storage system, comprising:
 storing one or more versions of an object in a memory of a secondary datacenter;   receiving, by the secondary datacenter, a delete request from a primary datacenter, wherein the delete request requests that the secondary datacenter delete portions of a specific version of the object stored by the secondary datacenter;   deleting at least a portion of a first version of the object from the memory of the second datacenter; and   sending, by the secondary datacenter, a delete response to the primary datacenter, wherein the delete response indicates that the specific version of the object was successfully deleted from the memory of the second datacenter when the delete response includes an entity tag associated with the specific version of the object.   
     
     
         14 . The method of  claim 13 , wherein the delete response indicates, to the primary datacenter, that an error occurred in the deletion of the object when the entity tag carried by the delete response does not match an entity tag associated with the specific version of the object. 
     
     
         15 . The method of  claim 13 , wherein the delete response indicates, to the primary datacenter, that the secondary datacenter did not verify that data deleted from the memory of the secondary datacenter corresponded to the specific version of the object when the delete response excludes an entity tag. 
     
     
         16 . The method of  claim 15 , wherein the secondary datacenter lacks the capability to recognize the first entity tag in the delete request. 
     
     
         17 . The method of  claim 13 , wherein deleting at least the portion of the first version of the object comprises deleting the entire first version of the object from the memory of the secondary datacenter. 
     
     
         18 . The method of  claim 13 , wherein deleting at least the portion of the first version of the object comprises deleting a first sub-portion of the first version of the object from the memory of the secondary datacenter, wherein a second sub-portion of the first version of the object remains stored in the memory of the secondary datacenter.

Join the waitlist — get patent alerts

Track US2015331902A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.