Intermediate write operation dispersed storage network frame

• US 9,244,879 B2
• Filed: 02/18/2014
• Issued: 01/26/2016
• Est. Priority Date: 04/26/2010
• Status: Expired due to Fees

• Current Assignee: Pure Storage, Inc.
• Original Assignee: International Business Machines Corporation
• Inventors: Baptist, Andrew, Leggette, Wesley, Resch, Jason K., Motwani, Manish
• Primary Examiner(s): Jiang, Charles C
• Assistant Examiner(s): KAMARA, MOHAMED A
• Application Number:
  US14/182,528
• Publication Number:
  US 20140161142A1
• Time in Patent Office: 707 Days
• Field of Search: 370/252, 370/400, 370/412, 370428-429, 370464-472, 370/474, 709/201, 709212-216, 709/243, 711100-173
• US Class Current: 1/1
• 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 generating write requests, wherein a write request includes a payload and a protocol header. The payload includes one or more slice payload sections and a transaction number field. The protocol header includes an operation code field that indicates a write operation. The method continues, when responses to the write requests are favorable, by generating write commit requests, wherein a write commit request includes a commit payload and a commit protocol header. The commit payload includes the transaction number and the commit protocol header includes the operation code field that indicates write commit operation. The method continues, when responses to the write requests are unfavorable, by generating write rollback requests, wherein a rollback request includes a rollback payload and a rollback protocol header. The rollback payload includes the transaction number and the rollback protocol header includes the operation code field that indicates write rollback operation.

Claims

1. A method for a processing module of a computing device to execute write request operation, the method comprises:

generating a plurality of write requests, wherein a write request command of the plurality of write request commands includes a payload and a protocol header, wherein the payload includes one or more slice payload sections, and a transaction number field that include a transaction number corresponding to the write request operation, and the protocol header includes a payload length field, an operation code field that indicates write operation, and other protocol header fields;

when responses to the plurality of write requests are favorable, generating a plurality of write commit requests, wherein a write commit request of the plurality of write commit requests includes a commit payload and a commit protocol header, wherein the commit payload includes the transaction number and the commit protocol header includes a request number field, a commit payload length, the operation code field that indicates write commit operation, and the other protocol header fields; and

when responses to the plurality of write requests are unfavorable, generating a plurality of write rollback requests, wherein a rollback request of the plurality of rollback requests includes a rollback payload and a rollback protocol header, wherein the rollback payload includes the transaction number and the rollback protocol header includes the request number field, a rollback payload length, the operation code field that indicates write rollback operation, and the other protocol header fields.

2. The method of claim 1, wherein the other protocol header fields comprise:

a protocol class field that indicates the write operation; and

a request/response field that indicates request for the plurality of write requests, the plurality of write commit requests, and the plurality of write rollback requests.

3. The method of claim 2, wherein the other protocol headers further comprise:

a protocol class version field to indicate a protocol class version for the write operation.

4. The method of claim 1 further comprises:

when responses to the plurality of write commit requests are favorable, generating a plurality of write finalize requests, wherein a write finalize request of the plurality of write finalize requests includes a finalize payload and a finalize protocol header, wherein the finalize payload includes the transaction number and the finalize protocol header includes the request number field, a finalize payload length, the operation code field that indicates write finalize operation, and the other protocol header fields; and

when responses to the plurality of write commit requests are unfavorable, generating a plurality of write undo requests, wherein an undo request of the plurality of undo requests includes an undo payload and an undo protocol header, wherein the undo payload includes slices names and the undo protocol header includes the request number field, an undo payload length, the operation code field that indicates write undo operation, and the other protocol header fields.

5. The method of claim 1, wherein a slice payload section of the one or more slice payload section comprises:

one or more slices names of one or more encoded data slices to be stored;

one or more corresponding slice revision numbers of the one or more encoded data slices; and

one or more corresponding slice lengths of the one or more encoded data slices.

6. A computer comprises:

an interface;

a memory; and

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

generate a plurality of write requests, wherein a write request command of the plurality of write request commands includes a payload and a protocol header, wherein the payload includes one or more slice payload sections, and a transaction number field that include a transaction number corresponding to a write request operation, and the protocol header includes a payload length field, an operation code field that indicates write operation, and other protocol header fields;

when responses to the plurality of write requests are favorable, generate a plurality of write commit requests, wherein a write commit request of the plurality of write commit requests includes a commit payload and a commit protocol header, wherein the commit payload includes the transaction number and the commit protocol header includes a request number field, a commit payload length, the operation code field that indicates write commit operation, and the other protocol header fields; and

when responses to the plurality of write requests are unfavorable, generate a plurality of write rollback requests, wherein a rollback request of the plurality of rollback requests includes a rollback payload and a rollback protocol header, wherein the rollback payload includes the transaction number and the rollback protocol header includes the request number field, a rollback payload length, the operation code field that indicates write rollback operation, and the other protocol header fields.

7. The computer of claim 6, wherein the other protocol header fields comprise:

a protocol class field that indicates the write operation; and

a request/response field that indicates request for the plurality of write requests, the plurality of write commit requests, and the plurality of write rollback requests.

8. The computer of claim 7, wherein the other protocol headers further comprise:

a protocol class version field to indicate a protocol class version for the write operation.

9. The computer of claim 6, wherein the processor is further operable to:

when responses to the plurality of write commit requests are favorable, generate a plurality of write finalize requests, wherein a write finalize request of the plurality of write finalize requests includes a finalize payload and a finalize protocol header, wherein the finalize payload includes the transaction number and the finalize protocol header includes the request number field, a finalize payload length, the operation code field that indicates write finalize operation, and the other protocol header fields; and

when responses to the plurality of write commit requests are unfavorable, generate a plurality of write undo requests, wherein an undo request of the plurality of undo requests includes an undo payload and an undo protocol header, wherein the undo payload includes slices names and the undo protocol header includes the request number field, an undo payload length, the operation code field that indicates write undo operation, and the other protocol header fields.

10. The computer of claim 6, wherein a slice payload section of the one or more slice payload section comprises:

one or more slices names of one or more encoded data slices to be stored;

one or more corresponding slice revision numbers of the one or more encoded data slices; and

one or more corresponding slice lengths of the one or more encoded data slices.

11. The computer of claim 6, wherein the processor comprises one or more of:

a microprocessor, a micro-controller, a digital signal processor, a microcomputer, a central processing unit, a field programmable gate array, a programmable logic device, a state machine, logic circuitry, an analog circuitry, a digital circuitry, and a device that manipulates signals based on at least one of hard coding of the device and operational instructions.

12. A computer readable storage device comprises:

a first memory section that stores operational instructions that, when executed by a processor, causes the processor to;

generate a plurality of write requests, wherein a write request command of the plurality of write request commands includes a payload and a protocol header, wherein the payload includes one or more slice payload sections, and a transaction number field that include a transaction number corresponding to a write request operation, and the protocol header includes a payload length field, an operation code field that indicates write operation, and other protocol header fields;

a second memory section that stores operational instructions that, when executed by the processor, causes the processor to;

when responses to the plurality of write requests are favorable, generate a plurality of write commit requests, wherein a write commit request of the plurality of write commit requests includes a commit payload and a commit protocol header, wherein the commit payload includes the transaction number and the commit protocol header includes a request number field, a commit payload length, the operation code field that indicates write commit operation, and the other protocol header fields; and

a third memory section that stores operational instructions that, when executed by the processor, causes the processor to;

when responses to the plurality of write requests are unfavorable, generate a plurality of write rollback requests, wherein a rollback request of the plurality of rollback requests includes a rollback payload and a rollback protocol header, wherein the rollback payload includes the transaction number and the rollback protocol header includes the request number field, a rollback payload length, the operation code field that indicates write rollback operation, and the other protocol header fields.

13. The computer readable storage device of claim 12, wherein the other protocol header fields comprise:

a protocol class field that indicates the write operation; and

a request/response field that indicates request for the plurality of write requests, the plurality of write commit requests, and the plurality of write rollback requests.

14. The computer readable storage device of claim 13, wherein the other protocol headers further comprise:

a protocol class version field to indicate a protocol class version for the write operation.

15. The computer readable storage device of claim 12 further comprises:

a fourth memory section that stores operational instructions that, when executed by the processor, causes the processor to;

when responses to the plurality of write commit requests are favorable, generate a plurality of write finalize requests, wherein a write finalize request of the plurality of write finalize requests includes a finalize payload and a finalize protocol header, wherein the finalize payload includes the transaction number and the finalize protocol header includes the request number field, a finalize payload length, the operation code field that indicates write finalize operation, and the other protocol header fields; and

a fifth memory section that stores operational instructions that, when executed by the processor, causes the processor to;

when responses to the plurality of write commit requests are unfavorable, generate a plurality of write undo requests, wherein an undo request of the plurality of undo requests includes an undo payload and an undo protocol header, wherein the undo payload includes slices names and the undo protocol header includes the request number field, an undo payload length, the operation code field that indicates write undo operation, and the other protocol header fields.

16. The computer readable storage device of claim 12 wherein a slice payload section of the one or more slice payload section comprises:

one or more slices names of one or more encoded data slices to be stored;

one or more corresponding slice revision numbers of the one or more encoded data slices; and

one or more corresponding slice lengths of the one or more encoded data slices.