For systems that allow checkpointing, the CHECKPOINT attribute for PREEMPTPOLICY allows a job to save its current state and either terminate or continue running. A checkpointed job may restart at any time and resume execution from its most recent checkpoint.

You can tune checkpointing behavior on a per-resource manager-basis by setting the CHECKPOINTSIG and CHECKPOINTTIMEOUT attributes of the RMCFG parameter.

The following outlines some benefits of using CHECKPOINT and also lists some things you should be aware of if you choose to use it.

Advantages:

• This attribute allows you to restart a job from its last checkpoint.

Cautions:

• Using CHECKPOINT, it takes a longer time for jobs to complete.

To use CHECKPOINT

Make the following configurations to the moab.cfg file:

GUARANTEEDPREEMPTION TRUE
PREEMPTPOLICY CHECKPOINT

QOSCFG[test1] QFLAGS=PREEMPTEE MEMBERULIST=john PRIORITY=100 
QOSCFG[test2] QFLAGS=PREEMPTOR MEMBERULIST=john PRIORITY=10000

1. Set GUARANTEEDPREEMPTION to TRUE. (This locks the job on a node and keeps trying to preempt.)
2. Make sure that JOBNODEMATCHPOLICY is not set to EXACTNDODE.
3. Set PREEMPTPOLCY to CHECKPOINT.

PREEMPTPOLICY CHECKPOINT

4. Make sure that the PREEMPTEE job has a lower priority than the PREEMPTOR job.

QOSCFG[test1] QFLAGS=PREEMPTEE MEMBERULIST=john PRIORITY=100
QOSCFG[test2] QFLAGS=PREEMPTOR MEMBERULIST=john PRIORITY=10000

See Also

• Choosing a PREEMPTPOLICY type