Method and apparatus for facilitating checkpointing of an application through an interceptor library

• US 20030088807A1
• Filed: 11/07/2001
• Published: 05/08/2003
• Est. Priority Date: 11/07/2001
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Brodie-Tyrrell, William F., Mathiske, Bernd J.W.
• Application Number:
  US10/039,704
• Publication Number:
  US 20030088807A1
• Time in Patent Office: Days
• US Class Current: 714/6
• CPC Class Codes: G06F 11/1438 Restarting or rejuvenating

Abstract

One embodiment of the present invention provides a system for intercepting function calls and recording their parameters to facilitate creating a checkpoint for an application. The system operates by directing function calls to an interceptor library created for the purpose of intercepting the function calls. Functions within this interceptor library record the parameters of the function call, and then make the original call upon receiving the result of the function call. The interceptor library functions forward the results back to the application. In this way, the system records state information without modifying the application or the operating system.

Claims

1. A method for checkpointing an application, comprising:

pre-linking an interceptor library into the application during a run-time invocation of the application, wherein the run-time invocation occurs after the application has been complied and linked;

intercepting a function call produced by the application at the interceptor library;

recording parameters of the function call to create a checkpoint that includes information about the function call parameters;

making the function call;

receiving results of the function call; and

forwarding results of the function call back to the application.

2. The method of claim 1, further comprising creating a checkpoint by:

stopping the application;

retrieving the recorded parameters;

saving the checkpoint data, including the recorded parameters, to secondary storage; and

resuming the application.

3. The method of claim 2, further comprising using the checkpoint to restore the application.

4. The method of claim 2, wherein saving the checkpoint data to secondary storage involves saving the checkpoint data to a persistent storage.

5. The method of claim 2, wherein saving the checkpoint data to secondary storage involves saving the checkpoint data in a file system, or a database.

6. The method of claim 1, wherein making the function call involves referencing the function through a function pointer.

7. The method of claim 1, further comprising recording the results of the function call to facilitate creating a checkpoint that includes information about the results of the function call.

8. The method of claim 1, wherein the function calls can include system calls or lib calls.

9. The method of claim 1, wherein the parameters can include:

file paths;

thread flags; and

timer-thread relationships.

10. A computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for checkpointing an application, the method comprising:

pre-linking an interceptor library into the application during a run-time invocation of the application, wherein the run-time invocation occurs after the application has been complied and linked;

intercepting a function call produced by the application at the interceptor library;

recording parameters of the function call to create a checkpoint that includes information about the function call parameters;

making the function call;

receiving results of the function call; and

forwarding results of the function call back to the application.

11. The computer-readable storage medium of claim 10, further comprising creating a checkpoint by:

stopping the application;

retrieving the recorded parameters;

saving the checkpoint data, including the recorded parameters, to secondary storage; and

resuming the application.

12. The computer-readable storage medium of claim 11, further comprising using the checkpoint to restore the application.

13. The computer-readable storage medium of claim 11, wherein saving the checkpoint data to secondary storage involves saving the checkpoint data to a persistent storage.

14. The computer-readable storage medium of claim 12, wherein saving the checkpoint data to secondary storage involves saving the checkpoint data in a file system, or a database.

15. The computer-readable storage medium of claim 10, wherein making the function call involves referencing the function through a function pointer.

16. The computer-readable storage medium of claim 10, wherein the method further comprises recording the results of the function call to facilitate creating a checkpoint that includes information about the results of the function call.

17. The computer-readable storage medium of claim 10, wherein the function calls can include system calls or lib calls.

18. The computer-readable storage medium of claim 10, wherein the parameters can include:

file paths;

thread flags; and

timer-thread relationships.

19. An apparatus that checkpoints an application, comprising:

a pre-linking mechanism that is configured to pre-link an interceptor library into the application during a run-time invocation of the application, wherein the run-time invocation occurs after the application has been complied and linked;

an intercepting mechanism within the interceptor library that is configured to intercept a function call produced by the application;

a recording mechanism that is configured to record parameters of the function call to facilitate creating a checkpoint that includes information about the function call parameters;

a calling mechanism that is configured to make the function call;

a receiving mechanism that is configured to receive results of the function call; and

a forwarding mechanism that is configured to forward results of the function call back to the application.

20. The apparatus of claim 19, further comprising a checkpoint creation mechanism that is configured to:

stop the application;

retrieve the recorded parameters;

save the checkpoint data, including the recorded parameters, to secondary storage; and

to

resume the application.

21. The apparatus of claim 20, further comprising a restoration mechanism that is configured to use the checkpoint data to restore the application to the checkpointed state.

22. The apparatus of claim 20, wherein the checkpoint creation mechanism is configured to save checkpoint data to a persistent storage.

23. The apparatus of claim 20, wherein the checkpoint creation mechanism is configured to save the checkpoint data in a file system, or a database.

24. The apparatus of claim 19, wherein the calling mechanism is configured to make the function call by referencing the function through a function pointer.

25. The apparatus of claim 19, further comprising a recording mechanism that is configured to record the results of the function call to facilitate creating a checkpoint that includes information about the results of the function call.

26. The apparatus of claim 19, wherein the function calls can include system calls or lib calls.

27. The apparatus of claim 19, wherein the parameters can include:

file paths;

thread flags; and

timer-thread relationships.