Long-running storage manageability operation management

• US 10,133,615 B2
• Filed: 03/15/2016
• Issued: 11/20/2018
• Est. Priority Date: 12/15/2015
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Hembram, Shyama Prasad, Franco, Gustavo Rafael
• Primary Examiner(s): Le, Dieu Minh T
• Application Number:
  US15/071,143
• Publication Number:
  US 20170168887A1
• Time in Patent Office: 980 Days
• Field of Search: 714 37, 714 381, 714 41, 714 15, 714 46
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 11/0772 Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

Serving resources. A method includes receiving from a client, a request for one or more operations to be performed. The method further includes attempting to perform the one or more operations. The method further includes determining that the one or more operations are not complete at a present time. As a result, the method further includes sending a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time. The method further includes receiving a request from the client for status information about the one or more operations. The method further includes repeating sending a message to the client and receiving a request from the client for status information.

Claims

1. A stateless system, configured to scale out and handle long running operations with a low operation failure rate, the system comprising:

one or more processors; and

one or more physical computer-readable storage media having stored thereon instructions that are executable by the one or more processors to configure the one or more processors to serve resources, including instructions that are executable to configure the one or more processors to perform at least the following

receiving from a client, a request for one or more asynchronous read/write operations to be performed on a datastore;

attempting to perform the one or more asynchronous read/write operations on the datastore;

determining that the one or more asynchronous read/write operations are not complete at a present time on the datastore;

as a result, sending a message to the client indicating that the client should attempt to obtain status information for the one or more asynchronous read/write operations on the datastore at a predetermined later time, including sending a unique operation id to the client identifying the one or more asynchronous read/write operations;

receiving a request from the client for status information about the one or more asynchronous, read/write, storage operations on the datastore, the request for status information comprising the unique operation id; and

repeating;

sending a message to the client indicating that the one or more asynchronous read/write operations are in progress and that the client should attempt to obtain status information for the one or more asynchronous read/write operations on the datastore at a predetermined later time;

receiving a request from the client for status information about the one or more operations until the one or more asynchronous read/write operations are complete, after which, indicating that the asynchronous read/write operations have been completed on the datastore or until a predetermined number of retries has been attempted, after which, failure is indicated to the client.

2. The system of claim 1, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to receive from the client an indication of a number of retries of the one or more asynchronous read/write operations that should be attempted on the datastore.

3. The system of claim 1, wherein sending a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time comprises sending a URI to the client, including the unique operation ID, that the client should use for one or more subsequent status requests by the client.

4. The system of claim 3, wherein sending a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time comprises sending a same URI to the client each time a message is sent to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time.

5. The system of claim 3, wherein sending a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time comprises sending a different URI to the client each time a message is sent to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time.

6. The system of claim 1, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to receive from the client an indication that no more retries should be attempted.

7. The system of claim 1, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to save operation context to a datastore such that operations can be replayed or retried without the client explicitly retrying the operations.

8. The system of claim 1, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the computer system to poll for operations that are eligible to run.

9. The system of claim 1, wherein attempting to perform the one or more operations is performed transactionally.

10. In a computing environment, a system for obtaining resources in a manner that facilitates long running operations with a low operation failure rate, the system comprising:

one or more processors; and

one or more physical computer-readable storage media having stored thereon instructions that are executable by the one or more processors to configure the one or more processors to obtain resources, including instructions that are executable to configure the one or more processors to perform at least the following;

at a client, sending a request to a server for one or more asynchronous read/write operations to be performed on a datastore;

receiving from the server, a message to the client indicating that the one or more asynchronous read/write operations are in progress and that the client should attempt to obtain status information for the one or more asynchronous read/write operations to determine the status of the one or more asynchronous read/write operations at a predetermined later time, the message including a unique operation id identifying the one or more asynchronous read/write operations;

in response, sending a request to the server for status information about the one or more asynchronous read/write operations on the datastore, the request for status information comprising the unique operation id; and

repeating receiving from the server, a message to the client indicating that the client should attempt to obtain status information for the one or more asynchronous read/write operations at a predetermined later time and sending a request to the server for status information about the one or more asynchronous read/write operations until the one or more asynchronous read/write operations are complete, after which completion status is received by the client or until a predetermined number of retries has been attempted, after which, failure is indicated to the client.

11. The system of claim 10, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to send to the server an indication of a number of retries of the one or more asynchronous read/write operations that should be attempted on the datastore.

12. The system of claim 10, wherein receiving from the server, a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time comprises receiving a URI, including the unique operation ID, that the client should use for one or more subsequent status information requests.

13. The system of claim 12, wherein a same URI for the resources is received by the client each time the client receives from the server, a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time.

14. The system of claim 12, wherein a different URI for the resources is received by the client each time the client receives from the server, a message to the client indicating that the client should attempt to obtain status information for the one or more operations at a predetermined later time.

15. The system of claim 10, wherein the one or more computer-readable storage media further have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to send an indication that no more retries should be attempted.

16. A stateless system , configured to scale out and handle long running operations with a low operation failure rate, the system comprising:

one or more physical processors; and

one or more physical computer-readable storage media;

wherein the one or more computer-readable storage media have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to implement a request handler configured to receive from a client, a request for one or more asynchronous read/write operations to be performed on a datastore;

wherein the one or more computer readable storage media have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to implement a background service configured to perform the one or more asynchronous read/write operations on the datastore;

wherein the request handler is further configured to determine that the one or more asynchronous read/write operations on the datastore are not complete; and

wherein the request handler is further configured to repeatedly send a message to the client indicating that the client should attempt to obtain status information for the one or more asynchronous read/write operations on the datastore at a predetermined later time, including sending a unique operation id to the client identifying the one or more asynchronous read/write operations until the one or more asynchronous read/write operations are complete, after which, the request handle is configured to indicate that the asynchronous read/write operations have been completed on the datastore or until a predetermined number of retries has been attempted, after which, failure is indicated to the client.

17. The system of claim 16, wherein the one or more computer readable storage media have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to implement a datastore configured to store asynchronous read/write operation details.

18. The system of claim 17, wherein the datastore supports transactional semantics.

19. The system of claim 16, wherein the one or more computer readable storage media have stored thereon instructions that are executable by the one or more processors to configure the one or more processors to implement a garbage collector configured to cleanup asynchronous read/write operations that have either been completed or have reached a maximum retry count.

20. The system of claim 16, wherein the system is configured to scale by supporting adding additional request handlers.