Persistent application activation and timer notifications

Patent metadata

Field	Value
Publication number	US-10162713-B2
Application number	US-201514625791-A
Country	US
Kind code	B2
Filing date	Feb 19, 2015
Priority date	Jan 15, 2010
Publication date	Dec 25, 2018
Grant date	Dec 25, 2018

Abstract

The present invention extends to methods, systems, and computer program products for persistent application activation and timer notifications. A durable instance manager, instance execution hosts, and an instance store interoperate to transition instances between executing and persisted states. System properties are associated with an instance. System properties can define re-activation conditions, that when satisfied, indicate that an instance is to be re-activated for execution. System properties can define timers as well as indications that instances are in a persisted but ready to run state.

First claim

What is claimed:

1. A system comprising memory operatively coupled to one or more processors, the memory storing instructions that perform a method of:
receiving, from a first instance execution host, a request to persist an application instance;
identifying a system property to re-activate the application instance, the system property comprising a timer;
tracking a state of the application instance from executing to persisted;
persisting the application instance for a duration of the timer;
determining, based on an expiration of the timer, that the application instance is to be running, wherein the expiration of the timer indicates the application instance is to be transitioned back to an executing state;
sending, based on the determination, an activation event to a second instance execution host to cause the second instance execution host to execute the application instance; and
tracking the state of the application instance from persisted to executing.

2. The system of claim 1 , wherein the application instance represents a portion of an application.

3. The system of claim 1 , further comprising:
prior to persisting the application instance, the first execution host being gracefully shutdown.

4. The system of claim 1 , further comprising:
receiving a load command to execute the application instance.

5. The system of claim 1 , wherein the first execution host and the second execution host are communicatively connected via a network.

6. The system of claim 1 , wherein the network is the Internet.

7. A computer readable storage device storing instructions that, when executed, are capable of performing a method of:
receiving, from a first instance execution host, a request to persist an application instance;
identifying a system property to re-activate the application instance, the system property comprising a timer;
tracking the state of the application instance from executing to persisted;
persisting the application instance for a duration of the timer;
determining, based on an expiration of the timer, that the application instance is to be, wherein the expiration of the timer indicates the application instance is to be transitioned back to an executing state;
sending, based on the determination, an activation event to a second instance execution host to cause the second instance execution host to execute the application instance; and
tracking the state of the application instance from persisted to executing.

8. The computer readable storage device of claim 7 , wherein the application instance represents a portion of an application.

9. The computer readable storage device of claim 7 , further comprising:
prior to persisting the application instance, the first execution host being gracefully shutdown.

10. The computer readable storage device of claim 7 , further comprising: receiving a load command to execute the application instance.

11. The computer readable storage device of claim 7 , wherein the first execution host and the second execution host are communicatively connected via a network.

12. The computer readable storage device of claim 7 , wherein the network is the Internet.

13. A computer implemented method comprising:
receiving, from a first instance execution host, a request to persist an application instance, the request indicative of a graceful shutdown;
identifying a system property to re-activate the application instance, the system property comprising a timer;
tracking the state of the application instance from executing to persisted;
persisting the application instance for a duration of the timer;
determining, based on an expiration of the timer, that the application instance is to be running, wherein the expiration of the timer indicates the application instance is to be transitioned back to an executing state;
sending, based on the determination, an activation event to a second instance execution host to cause the second instance execution host to execute the application instance; and
tracking the state of the application instance from persisted to executing.

14. The computer implemented of claim 13 , wherein the application instance represents a portion of an application.

15. The computer implemented of claim 13 , further comprising:
prior to persisting the application instance, the first execution host being gracefully shutdown.

16. The computer implemented of claim 13 , further comprising:
receiving a load command to execute the application instance.

17. The computer implemented of claim 13 , wherein the first execution host and the second execution host are communicatively connected via a network.

18. The system of claim 1 , wherein the timer is a specified wake up time.

19. The computer readable storage device of claim 7 , wherein the timer is a specified wake up time.

20. The method of claim 13 , wherein the wherein the timer is a specified wake up time.

21. The system of claim 1 , wherein identifying comprises scanning a database to identify the system property.

Assignees

• Microsoft Technology Licensing Llc

Inventors

• Taylor John A
• Allen Nicholas A
• Langley Stuart J
• Sedukhin Igor
• Brown Justin D
• Paramasivam Kartik

Classifications

• G06F11/1469 Primary

  Backup restoration techniques · CPC title

• G06F11/2041

  with more than one idle spare processing component · CPC title

• G06F9/485 Primary

  Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title

• G06F11/1438

  Restarting or rejuvenating · CPC title

• G06F11/2046

  where the redundant components share persistent storage (G06F11/2043 takes precedence) · CPC title