Gracefully degradable versioned storage systems

• US 20080313496A1
• Filed: 06/12/2007
• Published: 12/18/2008
• Est. Priority Date: 06/12/2007
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Prabhakaran, Vijayan, Ramasubramanian, Venugopalan, Zhou, Lidong, Levin, Roy, Thekkath, Chandramohan A.
• Granted Patent: US 7,849,354 B2
• Time in Patent Office: Days
• US Class Current: 714/15
• CPC Class Codes: G06F 11/1402 Saving, restoring, recovering or retrying
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality

Abstract

Multiple versions of data on different sets of machines allow a system to degrade gracefully even when experiencing excessive failures. When excessive failures cause the latest versions to be unavailable, the system becomes degraded, but still offers an old version if available. A most recent coherent set of the available older versions is found and provided. The degree of degradation increases gradually as the system experiences more and more failures. Graceful degradation is desirably complementary to fault tolerance.

Claims

1. A method for use in a distributed storage system, the method comprising:

maintaining a plurality of versions of a data item including a latest version and an older version;

entering a degraded state on the distributed storage system; and

if the latest version of the data item is unavailable in the degraded state, then using the older version of the data item during processing in the degraded state.

2. The method of claim 1, wherein entering the degraded state occurs when a number of failures exceeds a threshold.

3. The method of claim 2, further comprising using a fault tolerance mechanism associated with the distributed system to determine when the number of failures exceeds the threshold.

4. The method of claim 1, further comprising storing the versions of the data item prior to entering the degraded state.

5. The method of claim 1, further comprising providing an indication that the processing of the data item in the degraded state is based on the older version of the data item.

6. The method of claim 1, further comprising leaving the degraded state and returning to a normal operating state after the distributed storage system recovers.

7. The method of claim 1, wherein the plurality of versions of the data item include a plurality of older versions of the data item, each older version being associated with a different time based on storage of that older version of the data item.

8. The method of claim 7, wherein if the latest version of the data item is unavailable in the degraded state, then using the latest available older version of the data item during processing in the degraded state.

9. The method of claim 7, wherein the degraded state has a degree of degradation based on the version of the data item that is used during processing in the degraded state.

10. The method of claim 1, wherein a plurality of consistent degraded views of the distributed storage system is maintained during processing in the degraded state.

11. The method of claim 10, wherein the consistent degraded views are maintained using at least one of a timestamp-based design, a dependency-based design, or a weak-dependency-based design.

12. The method of claim 1, further comprising receiving additional versions of the data item while in the degraded state, branching the additional versions while in the degraded state using a plurality of branches, and merging the branches while in a normal operating state after the distributed storage system recovers.

13. The method of claim 1, wherein maintaining the plurality of versions of the data item comprises storing a timestamp for each version of the data item as metadata.

14. A distributed storage system comprising:

a versioned data store comprising a plurality of data storage devices across which a plurality of versions of a data item are stored, including a latest version and older versions; and

a processor that determines whether to enter a degraded state, and during processing in the degraded state, determines whether to use the latest version of the data item or one of the older versions of the data item.

15. The system of claim 14, further comprising a fault tolerance mechanism, wherein the degraded state is entered when a number of failures in the system exceeds the capability of the fault tolerance mechanism.

16. The system of claim 14, further comprising an index server that maintains an index that tracks the versions of the data item.

17. The system of claim 14, further comprising an output device for providing an indication to a user or a client that the processing of the data item in the degraded state is based on one of the older versions of the data item.

18. A method for use in a distributed storage system, the method comprising:

receiving an update to a version of a data item that is stored on a storage server;

creating a new version of the data item; and

storing the new version of the data item with metadata on a different storage server, the metadata for use to maintain consistent degraded views of the distributed storage system during processing in the degraded state.

19. The method of claim 18, wherein the metadata corresponds to at least one of a timestamp-based design, a dependency-based design, or a weak-dependency-based design.

20. The method of claim 18, further comprising determining whether the version of the data item that is stored on the storage server and the new version are coherent.