...
Reservations typically allocate 1-3 compute nodes from the short partition and students to request resources within the scope of the reservation, e.g. 1 core and 4GB memory.
The naming convention is PIRG-day, for example erth363-mon would be the name of the reservation for the class PIRG erth363 that meets on Monday’s.
To use a reservation in Open OnDemand (OOD), specify the reservation name and partition name where the nodes allocated to the reservation reside (default is short) in the corresponding text fields. With srun
or sbatch
include --reservation=erth363
and --partition=short
.
Reservation Behaviors worth noting:
Jobs that do not specify the correct partition containing the allocated nodes in the reservation will queue (PD) until killed when the reservation ends or are deleted by the user
Jobs submitted to the reservation before the StartTime will fail with a clear message in Open OnDemand ( OOD), “requested reservation is invalid”
Jobs requesting more cores than the reservation provides fail with a clear error message in OOD
Jobs requesting more memory than the reservation provides will queue (PD) until killed when the reservation ends or deleted by the user
Other jobs requesting memory available in the reservation are launched successfully
Jobs are launched successfully even when requesting more time than reservation duration
Jobs are killed once the reservation ends
...