Storing data in accordance with encoded data slice revision levels in a dispersed storage network

• US 10,503,594 B2
• Filed: 09/21/2018
• Issued: 12/10/2019
• Est. Priority Date: 04/26/2010
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Pure Storage, Inc.
• Inventors: Baptist, Andrew, Leggette, Wesley, Resch, Jason K.
• Primary Examiner(s): Tsai, Henry
• Assistant Examiner(s): Hassan, Aurangzeb
• Application Number:
  US16/138,753
• Publication Number:
  US 20190034274A1
• Time in Patent Office: 445 Days
• Field of Search: None
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0659 Command handling arrangements, e.g. command buffers, queues, command scheduling
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12

Abstract

A method includes sending, by a computing device of a dispersed storage network (DSN), a set of write request messages to a set of storage units of the DSN regarding a plurality of sets of encoded data slices. The method continues by receiving, from a first storage unit, a first write response message including a group of status messages, which indicate whether a corresponding revision level of each of the first encoded data slices is a next revision level in accordance with a current revision level. The method continues by interpreting the group of status messages to determine whether an encoded data slice of first encoded data slices has a revision level error. When the error, the method continues by flagging the encoded data slices for a rollback message and when no error, the method continues by flagging each encoded data slice for a write commit message.

Claims

1. A method comprises:

sending, by a computing device of a dispersed storage network (DSN), a set of write request messages to a set of storage units of the DSN regarding a plurality of sets of encoded data slices, wherein a first write request of the set of write requests includes a first group of slice payloads for first encoded data slices of each set of the plurality of sets of encoded data slices and a corresponding revision level of each of the first encoded data slices, and wherein a first storage unit of the set of storage units temporarily stores the first encoded data slices;

receiving, by the computing device from the first storage unit, a first write response message that includes a group of status messages, wherein the group of status messages are generated by the first storage unit based on determining whether the corresponding revision level of each of the first encoded data slices is a next revision level in accordance with a current revision level maintained by the first storage unit, and wherein a status message of the group of status messages includes one or more of;

an operation succeeded message, a transaction conflict due to another transaction locking access to an encoded data slice of the first encoded data slices stored by the first storage unit, an address error, the revision level error, and operation is not authorized for the encoded data slice of the first encoded data slices;

processing, by the computing device, the first write response message by;

interpreting the group of status messages to determine whether an encoded data slice of the first encoded data slices has a revision level error;

when the encoded data slice of the first encoded data slices has a revision level error, flagging the encoded data slices for a rollback message; and

flagging each encoded data slice of the first encoded data slices not having the revision level error for a write commit message.

2. The method of claim 1 further comprises:

generating, by the computing device, the first write request to include a protocol header and a payload section, wherein the payload section includes a transaction number associated with the first group of slice payloads, wherein a slice payload of the first group of slice payloads further includes one or more of a slice name field and a slice length field.

3. The method of claim 1 further comprises:

wherein a second write request of the set of write requests includes a second group of slice payloads for second encoded data slices of each set of the plurality of sets of encoded data slices and a corresponding revision level of each of the second encoded data slices, and wherein a second storage of the set of storage units temporarily stores the second encoded data slices;

receiving, by the computing device from a second storage unit, a second write response message that includes a second group of status messages, wherein the second group of status messages are generated by the second storage unit based on determining whether the corresponding revision level of each of the second encoded data slices is a next revision level in accordance with a current revision level maintained by the second storage unit;

processing, by the computing device, the second write response message by;

interpreting the group of status messages to determine whether a second encoded data slice of the second encoded data slices has a revision level error;

when the second encoded data slice of the second encoded data slices has the revision level error, flagging the second encoded data slices for a second rollback message; and

flagging each second encoded data slice of the second encoded data slices not having the revision level error for a second write commit message.

4. The method of claim 1 further comprises:

for each set of the plurality of sets of encoded data slices having a write threshold number of encoded data slices not having the revision level error, issuing, by the computing device, write commit commands; and

for each set of the plurality of sets of encoded data slices having less than the write threshold number of encoded data slices not having the revision level error, issuing, by the computing device, rollback commands.

5. A computing device of a dispersed storage network (DSN) comprises:

memory;

an interface; and

a processing module operably coupled to the memory and the interface, wherein the processing module is operable to;

send, via the interface, a set of write request messages to a set of storage units of the DSN regarding a plurality of sets of encoded data slices, wherein a first write request of the set of write requests includes a first group of slice payloads for first encoded data slices of each set of the plurality of sets of encoded data slices and a corresponding revision level of each of the first encoded data slices, and wherein a first storage unit of the set of storage units temporarily stores the first encoded data slices;

receive, from the first storage unit via the interface, a first write response message that includes a group of status messages, wherein the group of status messages are generated by the first storage unit based on determining whether the corresponding revision level of each of the first encoded data slices is a next revision level in accordance with a current revision level maintained by the first storage unit, and wherein a status message of the group of status messages includes one or more of;

an operation succeeded message, a transaction conflict due to another transaction locking access to an encoded data slice of the first encoded data slices stored by the first storage unit, an address error, the revision level error, and operation is not authorized for the encoded data slice of the first encoded data slices;

process the first write response message by;

interpreting the group of status messages to determine whether an encoded data slice of the first encoded data slices has a revision level error;

when the encoded data slice of the first encoded data slices has a revision level error, flagging the encoded data slices for a rollback message; and

flagging each encoded data slice of the first encoded data slices not having the revision level error for a write commit message.

6. The computing device of claim 5, wherein the processing module is further operable to:

generate the first write request to include a protocol header and a payload section, wherein the payload section includes a transaction number associated with the first group of slice payloads, wherein a slice payload of the first group of slice payloads further includes one or more of a slice name field and a slice length field.

7. The computing device of claim 5, wherein the processing module is further operable to:

wherein a second write request of the set of write requests includes a second group of slice payloads for second encoded data slices of each set of the plurality of sets of encoded data slices and a corresponding revision level of each of the second encoded data slices, and wherein a second storage unit of the set of storage units temporarily stores the second encoded data slices;

receive from a second storage unit via the interface, a second write response message that includes a second group of status messages, wherein the second group of status messages are generated by the second storage unit based on determining whether the corresponding revision level of each of the second encoded data slices is a next revision level in accordance with a current revision level maintained by the second storage unit;

process the second write response message by;

interpreting the group of status messages to determine whether a second encoded data slice of the second encoded data slices has a revision level error;

when the second encoded data slice of the second encoded data slices has the revision level error, flagging the second encoded data slices for a second rollback message; and

flagging each second encoded data slice of the second encoded data slices not having the revision level error for a second write commit message.

8. The computing device of claim 5, wherein the processing module is further operable to:

for each set of the plurality of sets of encoded data slices having a write threshold number of encoded data slices not having the revision level error, issue write commit commands; and

for each set of the plurality of sets of encoded data slices having less than the write threshold number of encoded data slices not having the revision level error, issue rollback commands.