Detail
Reference
Detail that matters once an application is actually being checkpointed.
Some more detailed info about CRaC is available on these pages:
- Best practices What to do and what to avoid when writing an application that will be checkpointed.
- Checkpoint engines Choosing the mechanism that takes the image, with -XX:CRaCEngine — what upstream ships, and what a vendor build may add.
- Debugging failures Diagnosing a checkpoint or restore that did not work.
- CPU features Why a restored image is tied to CPU features, and how to control that.
- File descriptor policies Telling the runtime what to do with each open file descriptor at checkpoint time.
In this section
5 pages
- Best practices What to do and what to avoid when writing an application that will be checkpointed.
- Checkpoint engines Choosing the mechanism that takes the image, with -XX:CRaCEngine — what upstream ships, and what a vendor build may add.
- Debugging failures Diagnosing a checkpoint or restore that did not work.
- CPU features Why a restored image is tied to CPU features, and how to control that.
- File descriptor policies Telling the runtime what to do with each open file descriptor at checkpoint time.