Session execution decision

Patent metadata

Field	Value
Publication number	US-9857974-B2
Application number	US-201414450804-A
Country	US
Kind code	B2
Filing date	Aug 4, 2014
Priority date	Oct 3, 2013
Publication date	Jan 2, 2018
Grant date	Jan 2, 2018

Abstract

A method includes a dispersed storage (DS) processing module receiving a request. The method continues by identifying a session associated with the request. The method continues by queueing one or more tasks associated with the request. The method continues by determining whether the session is still active. When the session is not active, the method continues by cancelling the one or more tasks associated with the session prior to execution. When the session is still active, the method continues by executing the first task of the one or more tasks when a task resource is available.

First claim

What is claimed is:

1. A method for execution by one or more processing modules of one or more computing devices of a dispersed storage network (DSN), the method comprises:
receiving a request, wherein the request comprises a read slice request for data;
identifying a session associated with the request;
queueing a task associated with the request and the session;
prior to being ready to execute the task, determining whether a decode threshold is met message is received, wherein the decode threshold is met message indicates that sufficient slices have been received to decode the data;
when the decode threshold is met message has been received, cancelling the task;
when the decode threshold is met message has not been received and when ready to execute the task, determining whether the session is still active based on a timeout or a detection of disconnection with a requesting entity or an end of session message has been received;
when the session is not active, cancelling the task; and
when the session is still active, executing the task when task resources are available.

2. The method of claim 1 further comprises determining whether the task resources are available to execute the task.

3. The method of claim 2 further comprises executing the task utilizing the available task resources.

4. The method of claim 1 , wherein the task resources comprise one or more of:
computer processing;
computer storage; and
communications.

5. The method of claim 1 , wherein the identifying a session includes one or more of:
receiving a session identifier;
initiating a query;
receiving a response;
assigning a new session number; and
obtaining a session from another storage unit.

6. The method of claim 1 , wherein the queuing includes looking up the task and storing the task in a queue.

7. The method of claim 1 , wherein the canceling includes removing the task from the queue.

8. The method of claim 1 , wherein the determining whether the session is still active includes one or more of:
receiving a resource indicator;
receiving an indication that a threat is available;
receiving an indication that an aggregated partial result threshold has been met;
initiating a query;
receiving a response;
performing a look up; and
de-prioritizing another task associated with the resources.

9. A computing device of a dispersed storage network (DSN) configured to:
receive a request, wherein the request comprises a read slice request for data;
identify a session associated with the request;
queue a task associated with the request and the session;
prior to being ready to execute the task, determine whether a decode threshold is met message has been received, wherein the decode threshold is met message indicates that sufficient slices have been received to decode the data;
when the decode threshold is met message has been received, cancelling the task;
when the decode threshold is met message has not been received and when ready to execute the task, determine whether the session is still active based on a timeout or a detection of disconnection with a requesting entity or an end of session message has been received;
when the session is not active, cancel the task; and
when the session is still active, execute the task when a task resource is available.

10. The computing device of claim 9 further comprises determining whether resources are available to execute the task.

11. The computing device of claim 9 , wherein the resources comprise one or more of:
computer processing;
computer storage; and
communications.

12. The computing device of claim 9 , wherein the identifying a session includes one or more of:
receiving a session identifier;
initiating a query;
receiving a response;
assigning a new session number; and
obtaining a session from another storage unit.

13. The computing device of claim 9 , wherein the canceling includes removing the task from the queue.

14. The computing device of claim 9 , wherein the determining whether the session is still active includes one or more of:
receiving a resource indicator;
receiving an indication that a threat is available;
receiving an indication that an aggregated partial result threshold has been met;
initiating a query;
receiving a response;
performing a look up; and
de-prioritizing another task associated with the resources.

Assignees

• Cleversafe Inc
• IBM

Inventors

• Baptist Andrew
• Kaczmarek Joseph Martin
• Vedpathak Yogesh Ramesh

Classifications

• G06F9/4881

  Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues · CPC title

• G06F3/0611

  in relation to response time · CPC title

• G06F21/6272

  by registering files or documents with a third party · CPC title

• G06F3/0604 Primary

  Improving or facilitating administration, e.g. storage management · CPC title

• G06F16/182

  Distributed file systems · CPC title