Reconciler for a distributed storage system

• US 10,061,790 B2
• Filed: 07/07/2015
• Issued: 08/28/2018
• Est. Priority Date: 07/07/2015
• Status: Active Grant

• Current Assignee: NVIDIA Corporation
• Original Assignee: SwiftStack Inc. (NVIDIA Corporation)
• Inventors: Gerrard, Clay, Luse, Paul, Merritt, Samuel N., Dickinson, John
• Primary Examiner(s): Aspinwall, Evan
• Application Number:
  US14/793,568
• Publication Number:
  US 20170011078A1
• Time in Patent Office: 1,148 Days
• Field of Search: 707736
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof

Abstract

A technique is applied to eventually converge on a single data storage strategy for any set of object data which had an inconsistent data storage strategy applied during storage while there was a network partition. This state could occur in instances of a highly available distributed object storage system which can store objects according to multiple data storage strategies. Upon the healing of a network partition, the technique discovers if multiple data storage strategies were applied to the object data stored during a network partition, deterministically identifies which data storage strategy represents the correct strategy, for example based on the log of state transitions requested by the client according to the API contract, and ensures that this strategy is consistently applied to all object data in the collection.

Claims

1. A computer implemented method for discovering and logging misplaced objects in a distributed object storage system, comprising:

providing a processor running at least one container replicator in said distributed object storage system, said container replicator discovering storage policy inconsistencies;

said container replicator recording each transaction in a container database;

said container replicator adding said inconsistencies to a misplaced objects container;

said container replicator using a log format to record a history of state transitions which result from a series of requests, wherein said history is recorded in a plurality of container replicas;

each container replica maintaining a set of three vectors that indicate when the container replica last recorded a PUT or DELETE and when these actions resulted in a change of the container replica'"'"'s status (created or deleted); and

said container replicator comparing log items in said history between two or more containers to determine a representation of said state transaction history which resulted in a current state.

2. The method of claim 1, further comprising:

said container replicator identifying objects with conflicting storage policies; and

when a conflicting object is identified, said container replicator copying said object'"'"'s row from said container database to a local misplaced objects container.

3. The method of claim 1, further comprising:

said container replicator creating a misplaced objects container when a misplaced objects container does not already exist.

4. The method of claim 1, further comprising:

a container reconciler periodically locating and processing any misplaced objects containers;

said container reconciler examining object rows in each misplaced objects container in descending order and then determining a correct policy; and

said container reconciler making calls to disputed containers and using timestamp information to determine which policy is the correct policy for the container.

5. The method of claim 4, further comprising:

when a container is created, said container reconciler updating PUT and STATUS with a time of that action;

when a container is deleted, said container reconciler updating DELETE with a time of that action;

when a time of a DELETE action is not nil and it is greater than a time of a PUT action, said container reconciler considering said container to be in a DELETED state, otherwise said container is CREATED; and

when status of a container changes from CREATED or DELETED, said container reconciler updating STATUS with a time of said change.

6. The method of claim 4, further comprising:

said container reconciler moving an object from an incorrect policy to the correct policy for the container.

7. The method of claim 4, further comprising:

said container reconciler applying object writes to a correct storage policy;

said container reconciler cleaning up writes to an incorrect storage policy which no longer apply and removing rows from misplaced objects containers;

when all rows are successfully reconciled, said container reconciler deleting any now empty misplaced objects containers; and

said reconciler continuing to process misplaced objects containers until all misplaced objects containers are reconciled and removed.