Session execution decision

• US 10,416,889 B2
• Filed: 11/22/2017
• Issued: 09/17/2019
• Est. Priority Date: 10/03/2013
• Status: Active Grant

• Current Assignee: Pure Storage, Inc.
• Original Assignee: Pure Storage, Inc.
• Inventors: Baptist, Andrew, Kaczmarek, Joseph Martin, Vedpathak, Yogesh Ramesh
• Primary Examiner(s): Hoang, Hieu T
• Application Number:
  US15/821,566
• Publication Number:
  US 20180095669A1
• Time in Patent Office: 664 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 12/1458 by checking the subject access rights
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/6272 by registering files or documents with a third party
• CPC Class Codes: G06F 2211/1028 Distributed, i.e. distributed RAID systems with parity
• CPC Class Codes: G06F 2212/1052 Security improvement
• CPC Class Codes: G06F 2212/154 Networked environment
• CPC Class Codes: G06F 2221/2149 Restricted operating environment
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/061 Improving I/O performance
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0622 in relation to access
• CPC Class Codes: G06F 3/0635 by changing the path, e.g. traffic rerouting, path reconfiguration
• CPC Class Codes: G06F 3/0637 Permissions
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0647 Migration mechanisms
• CPC Class Codes: G06F 3/0655 Vertical data movement, i.e. input-output transfer; data movement between one or more hosts and one or more storage devices
• CPC Class Codes: G06F 3/0665 : at area level, e.g. provisioning of virtual or logical volumes
• CPC Class Codes: G06F 3/067 : Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 3/0682 : Tape device
• CPC Class Codes: G06F 3/0689 : Disk arrays, e.g. RAID, JBOD
• CPC Class Codes: G06F 9/4881 : Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1095 : Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• 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 67/145 : avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session

Abstract

A method includes receiving, by a storage unit of a dispersed storage network (DSN) an access request for an encoded data a slice of a set of encoded data slices from a computing device of the DSN. The method further includes queueing, by the storage unit, the access request for the encoded data slice. The method further includes, prior to executing the access request, determining, by the storage unit, whether a session associated with the access request is still active and whether execution the access request for encoded data slice is still needed. When the session is still active and the execution of the access request for the encoded data slice is still needed, the method further includes executing, by the storage unit, the access request for the encoded data slice.

Claims

1. A method comprises:

receiving, by a storage unit of a dispersed storage network (DSN), a write request of a set of write requests, wherein the write request is for an encoded data slice of a set of encoded data slices and is from a computing device of the DSN;

queueing, by the storage unit, the write request for the encoded data slice;

prior to executing the write request, determining whether a write threshold is met message has been received, wherein the write threshold is met message indicates that a write threshold number of write requests of the set of write requests have been deemed successful;

when the write threshold is met message has not been received and when ready to execute the write request, determining, by the storage unit, whether a session associated with the write request is still active; and

when the session is still active, executing, by the storage unit, the write request for the encoded data slice.

2. The method of claim 1, wherein the determining whether the session associated with the write request is still active comprises one of:

determining, by the storage unit, that an end of session message has not been received;

determining, by the storage unit, that a timeout period has not yet expired; and

detecting, by the storage unit, that the storage unit is still connected to the computing device.

3. The method of claim 1 further comprises:

when the session is not active, cancelling the write request for the encoded data slice.

4. The method of claim 1 further comprises:

identifying, by the storage unit, the session.

5. The method of claim 4, wherein the identifying the session comprises one or more of:

receiving a session identifier;

initiating an inquiry;

receiving a response;

assigning a session number; and

receiving the session from another storage unit of the DSN.

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

an interface;

memory;

a queue; and

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

receive, via the interface, a write request of a set of write requests, wherein the write request is for an encoded data slice of a set of encoded data slices and is from a computing device of the DSN;

store the write request for the encoded data slice in the queue;

prior to executing the write request, determining whether a write threshold is met message has been received, wherein the write threshold is met message indicates that a write threshold number of write requests of the set of write requests have been deemed successful;

when the write threshold is message has not been received and when ready to execute the write request, determine whether a session associated with the access request is still active; and

when the session is still active, execute the write request for the encoded data slice.

7. The storage unit of claim 6, wherein the processing module is further operable to determine whether the session associated with the write request is still active by one of:

determining, by the storage unit, that an end of session message has not been received;

determining, by the storage unit, that a timeout period has not yet expired; and

detecting, by the storage unit, that the storage unit is still connected to the computing device.

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

when the session is not active, cancel the access request for the encoded data slice.

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

identify the session.

10. The storage unit of claim 9, wherein the processing module is further operable to identifying the session by one or more of:

receiving a session identifier;

initiating an inquiry;

receiving a response;

assigning a session number; and

receiving the session from another storage unit of the DSN.