Selecting data for storage in a dispersed storage network

• US 10,353,772 B2
• Filed: 05/31/2016
• Issued: 07/16/2019
• Est. Priority Date: 05/31/2016
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Baptist, Andrew D., Dhuse, Greg R., Khadiwala, Ravi V., Resch, Jason K.
• Primary Examiner(s): Le, Uyen T
• Application Number:
  US15/168,771
• Publication Number:
  US 20170344428A1
• Time in Patent Office: 1,141 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/0611 in relation to response time
• 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]

Abstract

A method includes receiving a first write request that includes a first encoded data slice, a slice name, a new revision level associated with the slice name, and a previous revision level associated with the slice name. The method further includes determining whether another write request from another requesting device is pending. The other write request includes another encoded data slice, the slice name, the new revision level, and the previous revision level. The method further includes when the other write request is pending, adding the first write request to a list of pending write requests for the slice name. The method further includes generating a write response to the first write request to include the list of pending write requests. The method further includes receiving a finalize request for the first or the other encoded data slice. The method further includes closing the list of pending write requests.

Claims

1. A method for execution by a storage unit of a dispersed storage network (DSN), the method comprises:

receiving, by the storage unit, a first write request from a first requesting device, wherein the first write request includes a first encoded data slice, a slice name, a new revision level associated with the slice name, and a previous revision level associated with the slice name;

determining, by the storage unit, whether another write request from another requesting device is pending, wherein the other write request includes another encoded data slice, the slice name, the new revision level associated with the slice name, and the previous revision level associated with the slice name; and

when the other write request is pending;

adding, by the storage unit, the first write request to a list of pending write requests for the slice name;

generating, by the storage unit, a write response to the first write request, wherein the write response includes the list of pending write requests;

receiving, by the storage unit, in response to the write response, a finalize request from the first requesting device to finalize storage of the first or the other encoded data slice; and

closing, by the storage unit, the list of pending write requests for the slice name.

2. The method of claim 1 further comprises:

when the finalize request is regarding the first encoded data slice;

deleting, by the storage unit, the other encoded data slice; and

updating, by the storage unit, a most current revision level to the new revision level.

3. The method of claim 2 further comprises:

the first write request including a first transaction value;

the other write request including a second transaction value; and

determining, by the storage unit, that the finalize request is regarding the first encoded data slice when the finalize request includes the first transaction value.

4. The method of claim 2 further comprises:

deleting, by the storage unit, a previously stored encoded data slice having the slice name and the previous revision level.

5. The method of claim 1 further comprises:

when another write request is not pending;

opening, by the storage unit, the list of pending write requests to include the first write request;

generating, by the storage unit, the write response to the first write request, wherein the write response includes the list of pending write requests;

receiving, by the storage unit, in response to the write response, a first finalize request to finalize storage of the first encoded data slice; and

closing, by the storage unit, the list of pending write requests for the slice name.

6. The method of claim 5 further comprises:

determining, by the storage unit, prior to receiving the first finalize request, whether the other write request is received;

when the other write request is received prior to receiving the first finalize request, updating, by the storage unit, the list of pending write requests to include the other write request;

receiving, by the storage unit, in response to the write response, the finalize request to finalize storage of the first or the other encoded data slice; and

closing, by the storage unit, the list of pending write requests for the slice name.

7. The method of claim 1 further comprises:

the first write request including a first transaction value;

the other write request including a second transaction value; and

the list of pending write requests includes an ordered list of the first and second transaction values.

8. A storage unit of a dispersed storage network (DSN) comprises:

an interface;

memory; and

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

receive, via the interface, a first write request from a first requesting device, wherein the first write request includes a first encoded data slice, a slice name, a new revision level associated with the slice name, and a previous revision level associated with the slice name;

determine whether another write request from another requesting device is pending, wherein the other write request includes another encoded data slice, the slice name, the new revision level associated with the slice name, and the previous revision level associated with the slice name; and

when the other write request is pending;

add the first write request to a list of pending write requests for the slice name;

generate a write response to the first write request, wherein the write response includes the list of pending write requests;

receive, via the interface and in response to the write response, a finalize request from the first requesting device to finalize storage of the first or the other encoded data slice; and

close the list of pending write requests for the slice name.

9. The storage unit of claim 8, wherein the processing module is further operable to:

when the finalize request is regarding the first encoded data slice;

delete the other encoded data slice; and

update a most current revision level to the new revision level.

10. The storage unit of claim 9 further comprises:

the first write request including a first transaction value;

the other write request including a second transaction value; and

wherein the processing module is further operable to determine that the finalize request is regarding the first encoded data slice when the finalize request includes the first transaction value.

11. The storage unit of claim 9, wherein the processing module is further operable to:

delete a previously stored encoded data slice having the slice name and the previous revision level.

12. The storage unit of claim 8, wherein the processing module is further operable to:

when another write request is not pending;

open the list of pending write requests to include the first write request;

generate a write response to the first write request, wherein the write response includes the list of pending write requests;

receive, via the interface and in response to the write response, a first finalize request to finalize storage of the first encoded data slice; and

close the list of pending write requests for the slice name.

13. The storage unit of claim 12, wherein the processing module is further operable to:

determine, prior to receiving the first finalize request, whether the other write request is received;

when the other write request is received prior to receiving the first finalize request, update the list of pending write requests to include the other write request;

receive, via the interface and in response to the write response, the finalize request to finalize storage of the first or the other encoded data slice; and

close the list of pending write requests for the slice name.

14. The storage unit of claim 8 further comprises:

the first write request including a first transaction value;

the other write request including a second transaction value; and

the list of pending write requests includes an ordered list of the first and second transaction values.

15. A computer readable storage device comprises:

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

receive a first write request from a first requesting device, wherein the first write request includes a first encoded data slice, a slice name, a new revision level associated with the slice name, and a previous revision level associated with the slice name;

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

determine whether another write request from another requesting device is pending, wherein the other write request includes another encoded data slice, the slice name, the new revision level associated with the slice name, and the previous revision level associated with the slice name; and

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

when the other write request is pending;

add the first write request to a list of pending write requests for the slice name;

generate a write response to the first write request, wherein the write response includes the list of pending write requests;

receive, in response to the write response, a finalize request from the first requesting device to finalize storage of the first or the other encoded data slice; and

close the list of pending write requests for the slice name.

16. The computer readable storage device of claim 15, wherein the third memory section further stores operational instructions that, when executed by the storage unit, causes the storage unit to:

when the finalize request is regarding the first encoded data slice;

delete the other encoded data slice; and

update a most current revision level to the new revision level.

17. The computer readable storage device of claim 16 further comprises:

the first write request including a first transaction value;

the other write request including a second transaction value; and

the third memory section further stores operational instructions that, when executed by the storage unit, causes the storage unit to;

determine that the finalize request is regarding the first encoded data slice when the finalize request includes the first transaction value.

18. The computer readable storage device of claim 16, wherein the third memory section further stores operational instructions that, when executed by the storage unit, causes the storage unit to:

delete a previously stored encoded data slice having the slice name and the previous revision level.

19. The computer readable storage device of claim 15, wherein the third memory section further stores operational instructions that, when executed by the storage unit, causes the storage unit to:

when another write request is not pending;

open the list of pending write requests to include the first write request;

generate a write response to the first write request, wherein the write response includes the list of pending write requests;

receive, in response to the write response, a first finalize request to finalize storage of the first encoded data slice; and

close the list of pending write requests for the slice name.

20. The computer readable storage device of claim 19, wherein the third memory section further stores operational instructions that, when executed by the storage unit, causes the storage unit to:

determine, prior to receiving the first finalize request, whether the other write request is received;

when the other write request is received prior to receiving the first finalize request, update the list of pending write requests to include the other write request;

receive, in response to the write response, the finalize request to finalize storage of the first or the other encoded data slice; and

close the list of pending write requests for the slice name.