Conclusive write operation dispersed storage network frame

• US 9,807,171 B2
• Filed: 11/08/2016
• Issued: 10/31/2017
• Est. Priority Date: 04/26/2010
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Baptist, Andrew, Leggette, Wesley, Resch, Jason K., Mark, Zachary J., Volvovski, Ilya
• Primary Examiner(s): KAMARA, MOHAMED A
• Application Number:
  US15/346,375
• Publication Number:
  US 20170054809A1
• Time in Patent Office: 357 Days
• CPC Class Codes: G06F 11/1076 Parity data used in redundant arrays of independent storages, e.g. in RAID systems
• CPC Class Codes: G06F 15/167 using a common memory, e.g. mailbox
• 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/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/065 Replication mechanisms
• 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 begins by a processing module generating a payload of a dispersed storage network frame regarding a conclusive write request operation by generating one or more slice name fields of a payload to include one or more slice names corresponding to one or more write commit responses of a write request operation, wherein the conclusive write request operation is a conclusive phase of the write request operation. The method continues with the processing module generating one or more slice revision numbering fields of the payload, wherein each slice revision numbering field includes a slice revision number corresponding to an associated slice name of the one or more slice names. The method continues with the processing module generating a protocol header of the DSN frame by generating a payload length field of the protocol header to include a payload length and generating remaining fields of the protocol header.

Claims

1. A computer readable memory comprises:

a first memory section storing operational instructions that, when executed by a computing device, causes the computer device to;

generate a protocol header of a dispersed storage network (DSN) frame by;

generating an operation code field to indicate a conclusive write response operation;

generating a request number field to include a request number associated with the conclusive write request operation; and

generating remaining fields of the protocol header.

2. The computer readable memory of claim 1, wherein the first memory section further stores operational instructions that, when executed by the computing device, causes the computer device to generate the operation code field of the protocol header further by at least one of:

generating the operation code field to indicate a finalize write response operation when a threshold number of the one or more write commit responses have been received;

generating the operation code field to indicate an undo write response operation when the threshold number of the one or more write commit responses have not been received; and

extracting an operational code from a corresponding conclusive write request message.

3. The computer readable memory of claim 1, wherein the first memory section further stores operational instructions that, when executed by the computing device, causes the computer device to generate the remaining fields of the protocol header by at least one of:

generating a protocol class field to indicate a protocol class for the conclusive write response operation;

generating a protocol class version field for the conclusive write response operation;

generating a payload length field of the protocol header to include a predetermined payload length value; and

generating a request/response field to indicate a response message.

4. The computer readable memory of claim 3 further comprises:

a second memory section storing operational instructions that, when executed by the computing device, causes the computer device to;

output, in order, the protocol class field, the protocol class version field, the operation code field, the request/response field, the request number field, and the payload length field.

5. A method for execution by one or more computing devices of a dispersed storage network (DSN), the method comprises:

generating a set of dispersed storage network (DSN) frames regarding a conclusive write request operation, wherein generating the set of DSN frames includes;

generating a common protocol header for each of the set of DSN frames, wherein the common protocol header includes common information regarding the conclusive write request operation; and

generating a set of unique payload sections for the set of DSN frames, wherein generating a unique payload section of the set of unique payload sections includes;

generating one or more slice name fields of the payload to include one or more slice names corresponding to one or more write commit responses of a write request operation, wherein the conclusive write request operation is a conclusive phase of the write request operation; and

generating one or more slice revision numbering fields of the payload, wherein each slice revision numbering field includes a slice revision number corresponding to an associated slice name of the one or more slice names; and

sending the set of DSN frames to a set of storage units, wherein one of the set of DSN frames includes the common protocol header and one of the set of unique payload sections.

6. The method of claim 5, wherein the generating the common protocol header comprises:

generating a payload length field of the protocol header to include a payload length that represents length of the one or more slice name fields and length the one or more slice revision numbering fields; and

generating remaining fields of the protocol header.

7. The method of claim 5, wherein generating remaining fields of the protocol header comprises at least one of:

generating an operation code field to indicate a finalize write request operation when a threshold number of the one or more write commit responses have been received;

generating a protocol class field to indicate a protocol class for the finalize write request operation when the threshold number of the one or more write commit responses have been received; and

generating a protocol class version field to indicate a protocol class version for the finalize write request operation when the threshold number of the one or more write commit responses have been received.

8. The method of claim 5, wherein generating remaining fields of the protocol header comprises at least one of:

generating the operation code field to indicate an undo write request operation when a threshold number of the one or more write commit responses have not been received;

generating the protocol class field to indicate a protocol class for the undo write request operation when the threshold number of the one or more write commit responses have not been received; and

generating the protocol class version field to indicate a protocol class version for the undo write request operation when the threshold number of the one or more write commit responses have not been received.

9. The method of claim 8, wherein the generating the one or more slice names comprises at least one of:

receiving the one or more slice names; and

selecting the one or more slice names from a slice names list.