Selective checkpointing mechanism for application components

• US 7,165,186 B1
• Filed: 10/07/2003
• Issued: 01/16/2007
• Est. Priority Date: 10/07/2003
• Status: Active Grant

• Current Assignee: Oracle America, Inc. (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Viswanatham, Satish C., Duvur, Sreeram, Ebbs, Kenneth, Islam, Akm Nazrul, Basler, Mark, Cable, Laurence P.
• Primary Examiner(s): Iqbal; Nadeem
• Application Number:
  US10/681,010
• Time in Patent Office: 1,197 Days
• Field of Search: 714/1, 714/2, 714/4, 714/6, 714/11, 714/13, 714/15, 714/47, 709/105, 709/106
• US Class Current: 714/1
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating

Abstract

A system and method for selectively checkpointing application components. In one embodiment this method may include deploying a plurality of application components on a server, determining checkpoint information for each application component on the server, and selectively checkpointing each component during execution of each component according to the checkpoint information for each component. In one embodiment the checkpoint information may be provided by a checkpoint selection heuristic, which makes checkpoint selections based on a description of one or more methods of the application component. In one embodiment the checkpoint information may be provided by a deployment descriptor, which may have multiple overriding tiers to facilitate precise selection of methods, components and modules for checkpointing. In one embodiment the checkpoint and activation process may include callback routines which prepare an application component for checkpointing and activation.

Claims

1. A method, comprising:

deploying a plurality of application components on a server;

determining checkpoint information for each application component, wherein said determining the checkpoint information comprises applying a checkpoint selection heuristic to an application component, wherein said applying the checkpoint selection heuristic comprises selecting checkpoints based on a description of one or more methods of the application component; and

selectively checkpointing each component during execution of each component, according to the checkpoint information for each component.

2. The method of claim 1, wherein said applying the checkpoint selection heuristic to each application component comprises determining which of the one or more methods of the application component modifies the state of the component based on the description of the one or more methods.

3. The method of claim 1, wherein said determining the checkpoint information comprises indicating the checkpoint information with a deployment descriptor.

4. The method of claim 3, wherein said indicating the checkpoint information comprises indicating at a component descriptor level whether one or more methods in an application component should or should not be checkpointed.

5. The method of claim 4, wherein said indicating the checkpoint information comprises indicating at a module descriptor level whether all application components associated with a module should or should not be checkpointed.

6. The method of claim 5, wherein said indicating the checkpoint information comprises indicating at an application descriptor level whether all application components associated with an application should or should not be checkpointed.

7. The method of claim 6,

wherein said indicating at a component descriptor level overrides said indicating at a module descriptor level;

and

wherein said indicating at a module descriptor level overrides said indicating at an application descriptor level.

8. The method of claim 3, wherein said indicating the checkpoint information comprises indicating that checkpointing should occur after executing a method.

9. The method of claim 3, wherein said indicating the checkpoint information comprises indicating that checkpointing should occur after executing a transaction.

10. The method of claim 1 further comprising:

determining that an application component implements a first callback subroutine; and

executing the first callback subroutine prior to said selective checkpointing in response to said determining, wherein said first callback routine prepares said application component for checkpointing.

11. The method of claim 1, further comprising reactivating an application component in response to a server failure.

12. The method of claim 11, further comprising:

determining that an application component implements a second callback subroutine; and

executing a second callback routine prior to said reactivating of said application component in response to said determining;

wherein said callback routine prepares said application component for said reactivating.

13. A distributed system, comprising:

a first server;

a plurality of application components operable to execute on said first server;

said first server comprising a checkpointing mechanism;

wherein said checkpointing mechanism is operable to;

determine that an application component of the plurality of application components implements a first callback routine,

execute said first callback subroutine, wherein said first callback routine prepares the application component for selective checkpointing; and

selectively checkpoint the plurality of components during execution of said components according to checkpoint information associated with each of said application components.

14. The system of claim 13, wherein said checkpointing mechanism is operable to execute a checkpoint selection heuristic, wherein the checkpoint selection heuristic makes checkpoint selections based on a description of one or more methods of the application component.

15. The system of claim 13, further comprising a deployment descriptor operable to indicate said checkpoint information.

16. The system of claim 15, wherein said deployment descriptor comprises an application descriptor level operable to indicate that all application components associated with an application should or should not be checkpointed.

17. The system of claim 16, wherein said deployment descriptor comprises a module descriptor level operable to indicate that all application components associated with a module should or should not be checkpointed.

18. The system of claim 17, wherein said deployment descriptor comprises a component descriptor level operable to indicate that one or more methods in an application component should or should not be checkpointed.

19. The system of claim 18,

wherein said component descriptor level is operable to override said module descriptor level;

and

wherein said module descriptor level is operable to override said application descriptor level.

20. The system of claim 15, wherein said deployment descriptor is operable to indicate that checkpointing should occur after executing a method.

21. The system of claim 15, wherein said deployment descriptor is operable to indicate that checkpointing should occur after executing a transaction.

22. The system of claim 13, wherein said distributed system further comprises a second server, wherein said second server is operable to reactivate a backup application component in response to a failure of said first server.

23. The system of claim 22, wherein said checkpointing mechanism is operable to execute a second callback routine, wherein said callback routine prepares said application component for said reactivating.

24. A computer accessible storage medium operable to store program instructions for a method comprising:

deploying a plurality of application components on a server;

determining checkpoint information for each application component, wherein said determining the checkpoint information comprises applying a checkpoint selection heuristic to an application component, wherein said applying the checkpoint selection heuristic comprises selecting checkpoints based on a description of one or more methods of the application component; and

selectively checkpointing each component during execution of each component, according to the checkpoint information for each component.

25. The computer accessible medium of claim 24, wherein said applying the checkpoint selection heuristic to each application component comprises determining which of the one or more methods of the application component modifies the state of the component based on the description of the one or more methods.

26. The computer accessible medium of claim 24, wherein said determining the checkpoint information comprises indicating the checkpoint information with a deployment descriptor.

27. The computer accessible medium of claim 26, wherein said indicating the checkpoint information comprises indicating at a component descriptor level whether one or more methods in an application component should or should not be checkpointed.

28. The computer accessible medium of claim 27, wherein said indicating the checkpoint information comprises indicating at a module descriptor level whether all application components associated with a module should or should not be checkpointed.

29. The computer accessible medium of claim 28, wherein said indicating the checkpoint information comprises indicating at an application descriptor level whether all application components associated with an application should or should not be checkpointed.

30. The computer accessible medium of claim 29,

wherein said indicating at a component descriptor level overrides said indicating at a module descriptor level;

and

wherein said indicating at a module descriptor level overrides said indicating at an application descriptor level.

31. The computer accessible medium of claim 26, wherein said indicating the checkpoint information comprises indicating that checkpointing should occur after executing a method.

32. The computer accessible medium of claim 26, wherein said indicating the checkpoint information comprises indicating that checkpointing should occur after executing a transaction.

33. The computer accessible medium of claim 24 further comprising:

determining that an application component implements a first callback subroutine; and

executing the first callback subroutine prior to said selective checkpointing in response to said determining, wherein said first callback routine prepares said application component for said selective checkpointing.

34. The computer accessible medium of claim 24, further comprising reactivating an application component in response to a server failure.

35. The computer accessible medium of claim 34, further comprising:

determining that an application component implements a second callback subroutine;

executing a second callback routine prior to said reactivating of said application component in response to said determining; and

wherein said callback routine prepares said application component for said reactivating.

36. A method, comprising:

deploying a plurality of application components on a server;

determining checkpoint information for each application component, wherein said determining the checkpoint information comprises indicating the checkpoint information with a deployment descriptor, wherein said indicating the checkpoint information comprises;

indicating at a component descriptor level whether one or more methods in an application component should or should not be checkpointed;

indicating at a module descriptor level whether all application components associated with a module should or should not be checkpointed;

indicating at an application descriptor level whether all application components associated with an application should or should not be checkpointed;

wherein said indicating at a component descriptor level overrides said indicating at a module descriptor level; and

wherein said indicating at a module descriptor level overrides said indicating at an application descriptor level; and

selectively checkpointing each component during execution of each component, according to the checkpoint information for each component.