Amazon Technologies, Inc.

Carl Yates Perry

Praveen Kumar Gattu

Derek Ernest Denny-Brown, Ii

Christopher Henning Elving

Jeffrey Michael Barber

Methods and apparatus for lifecycle support for storage objects are disclosed. A storage medium stores program instructions that when executed on a processor implement a storage lifecycle manager of a multi-tenant storage service. The lifecycle manager determines a lifecycle policy to be implemented for a storage object. The policy indicates lifecycle transitions of the object, including a transition from a first service level to a second service level. The first service level and the second service level may each specify a maximum number of versions of the storage object. The lifecycle manager initiates modification operations corresponding to the storage object's data in accordance with the lifecycle policy, and verifies that the modification operations succeeded. The lifecycle manager provides, in response to a query, an indication of a current service level of the storage object.

Lifecycle transition validation for storage objects

Methods and apparatus for a pipelined architecture for storage lifecycles are disclosed. A method includes identifying, during a transition candidate discovery iteration, storage objects of a multi-tenant service for which respective lifecycle transitions are to be scheduled, including a particular storage object identified as being a candidate for a particular lifecycle transition. The method includes generating transition job objects, each job comprising respective indications of one or more of the storage objects identified during the discovery iteration. The method includes assigning, during a transition execution iteration, resources to initiate storage operations for the particular lifecycle transition, and initiating, using the assigned resources, storage operations for the particular lifecycle transition.

Storage lifecycle pipeline architecture

Multi-tenant storage service object lifecycle management using transition job objects

Lifecycle support for storage objects having multiple durability levels specifying different numbers of versions

Methods and apparatus for equitable resource allocation for storage object deletions are disclosed. A storage medium stores program instructions that when executed on a processor implement a deletion task dispatcher of a multi-tenant storage service. The dispatcher identifies one or more deletion job objects that each comprise an indication of a respective set of storage objects that are candidates for scheduled deletion from the storage service. The dispatcher determines a set of resources to be used for deletion operations corresponding to a particular deletion job object, based at least in part on the number of distinct clients whose storage objects are indicated in the job object, and assigned the set of resource to initiate the deletion operations corresponding to the particular job object.

Equitable resource allocation for storage object deletion

Methods and apparatus for storage lifecycle configuration management are disclosed. A storage medium stores program instructions that, when executed on a processor, implement a storage lifecycle manager. The manager receives a lifecycle policy to be applied to storage objects of a container of a storage service. The policy indicates lifecycle transitions to be implemented for the objects. The manager stores (a) a policy modification sequence number (PMSN) indicative of a most recent modification of the policy and (b) a policy application sequence number (PASN) associated with the particular logical container, where the PASN is based on the PMSN. The manager later compares the PMSN and the PASN to determine whether a lifecycle transition is to be performed, and if the transition is to be performed, schedules one or more operations for the transition.

Storage service lifecycle policy transition management

Methods and apparatus for backoff-based scheduling of storage object deletions are disclosed. A storage medium stores program instructions that when executed on a processor, obtain an indication of a collection of storage objects of a network-accessible multi-tenant storage service to be deleted in accordance with specified deletion criteria. A deletion of a storage object comprises a metadata deletion operation and one or more other operations. The instructions initiate, corresponding to at least some objects of the collection, respective metadata deletion operations at a metadata node of the storage service. If a metric associated with the metadata node meets a threshold criterion, the instructions delay, by a particular amount of time, an initiation of an operation corresponding to a deletion of another storage object.

Backoff-based scheduling of storage object deletions

Methods and apparatus for storage object deletion job management are disclosed. A storage medium stores program instructions that when executed on a processor, identify, during a particular deletion execution iteration, a particular deletion job object stored at a multi-tenant storage service, wherein the particular deletion job object indicates a collection of storage objects that are eligible for deletion from the storage service in accordance with specified deletion criteria. The instructions determine, based on a job validity criterion, whether deletion operations corresponding to the particular deletion job object of the one or more deletion job objects are to be scheduled. If the job object is validated, the instructions initiate a deletion operation for storage objects indicated in the particular deletion job object.

Storage object deletion job management

Methods and apparatus for conditional deletes of storage objects are disclosed. A storage medium comprises program instructions that when executed, implement a metadata node of a storage service in which a protocol based on sequence numbers is used to resolve update conflicts. The instructions store, as part of a conditional deletion record associated with a key of a particular storage object identified as a deletion candidate, a deletion sequence number derived from a particular modification sequence number of the object. In accordance with the protocol, the instructions determine whether an additional modification sequence number larger than the deletion sequence number has been generated in response to an operation associated with the key. If such an additional sequence number has been generated, the deletion of the storage object is canceled.

Growing community of inventors

Seattle, WA, United States of America

Carl Yates Perry