In this article
A retained disk is not a retained process. Demonstrate continuation from written artifacts after the old process is unavailable, and distinguish checkpoints from disk snapshots.
For a Yandex Cloud preemptible GPU VM, save useful results regularly and test application restart. A stopped VM can retain disk data without preserving the running calculation’s memory. Continuation needs explicit recorded state on storage with a known lifecycle.
Account for interruption rules
The preemptible-VM documentation describes forced stops when capacity is required and a maximum lifetime for a run. Do not schedule an uninterrupted calculation on the assumption it will continue until a convenient checkpoint.
Use the mode for work that tolerates pauses and retries. If the deadline cannot absorb either, evaluate an appropriate non-preemptible arrangement first. A lower compute rate alone does not compensate for a missed working window or a large repeated calculation.
Separate files from process memory
Define the latest valid checkpoint and how the next process finds it. A half-written file should not be counted as completed work. For independent jobs, save input identifiers and processing version alongside result status.
For a connected calculation, specify parameters, intermediate state and input references. A file labelled checkpoint is insufficient if restoration requires inspecting a variable in the previous live session. Add that missing information and repeat the small recovery test.
Use snapshots for their actual role
A disk snapshot is a separate mechanism for restoring disk state. It is not an automatic copy of all running application memory. Consider consistency at the capture point and the supported snapshot procedure.
| Object | Purpose |
|---|---|
| Application checkpoint | Continue from a defined calculation stage |
| Persistent disk | Retain written files |
| Snapshot | Restore disk state |
| Code and configuration | Recreate environment and parameters |
Snapshot expense and retention are independent decisions. Assign an owner and review date rather than leaving every old experiment copy indefinitely.
Exercise continuation deliberately
A team processing an archive can save completed blocks and a journal. In a controlled test, stop during a block and restart. The programme should reject incomplete output, avoid duplicates and continue from the appropriate place.
Keep code identity with saved state. Mixing artifacts from changed code can invalidate the result even when every file remains readable. Use shutdown signals for a quick final save, but rely primarily on regular preservation. Keep a short recovery-test log with the recipe and repeat it after meaningful application changes. That establishes resilience instead of relying on one old uninterrupted success.
Turn the check into a practical next step
A retained disk is not a retained process. Demonstrate continuation from written artifacts after the old process is unavailable, and distinguish checkpoints from disk snapshots.
For the documented details, consult the primary documentation; configuration reference. Continue with yandex gpu platform configuration and cloud gpu ephemeral vs persistent checklist.