QRSUB(1) | Grid Engine User Commands | QRSUB(1) |
qrsub - Submit an Advance Reservation (AR) to Grid Engine.
qrsub [-a date_time] [-A account_string] [-ckpt ckpt_name] [-d time] [-e date_time] [-he yes|no] [-help] [-l resource_list] [-now] [-M user[@host],...] [-N ar_name] [-w e|v] [-pe pe_name slot_range] [-q wc_queue_list] [-u wc_user_list]
Qrsub provides a means for operators, managers or users referenced in the ACL (see access_list(5)) "arusers" to create an Advance Reservation (AR) in the Grid Engine queuing system. ARs allow reserving particular consumable resources for future use. These reserved resources are only available for jobs requesting the AR, and the scheduler ensures the availability of the resources when the start time is reached. Jobs requesting the AR can only use the reserved consumable resources.
During AR submit time the Grid Engine queuing system selects the best suited queues for the AR request and then reserves the desired amount of resources. For a reservation, all queues that are not in orphaned state are considered as suited. Only if the AR request can be fulfilled will the AR be granted.
ARs will be deleted either automatically when the end time is reached, or manually using qrdel(1). In both cases, first all jobs requesting the AR will be removed and then the AR itself. Already granted ARs can be shown with qrstat(1).
Note: To make AR behavior predictable, it is necessary to have reserved resources available at the time of AR start. This is done by keeping jobs with a unlimited runtime limit separated from ARs, and not considering resources used by such jobs for reservation.
Note: Resource Quotas are not considered for AR queue selection, nor for jobs requesting an AR.
When an AR was successfully added to the Grid Engine queuing system qrsub returns a unique integer ID referring to the the newly created AR. The highest AR ID is 9999999. If the highest ID is reached, a wraparound happens and the next unused ID, starting with 1, will be used.
For qrsub, the administrator and the user may define
default request files (analogous to Grid Engine_request for qsub), which can
contain any of the possible command line options.
A cluster wide default request file is optional. If such a default request
file is used, it must be placed under
$SGE_ROOT/$SGE_CELL/common/sge_ar_request (global defaults file).
A user private default request file is optional. If it is used, it must be
placed under
$HOME/.sge_ar_request (user private defaults file).
A hard error, "-he yes", means as long as the
AR is in error state no jobs using the AR will be scheduled. If soft
error, "-he no", is specified the AR stays usable with
the remaining resources.
By default soft error handling is used.
b Mail is sent at the beginning of the AR e Mail is sent at the end of the AR a Mail is sent when the AR goes into error state n No mail is sent, default for qrsub
This option is used to reserve the proper queues to match this request if it would be requested by a qsub. A more detailed description of wc_queue_list can be found in sge_types(5).
The specifiers e and v define the following validation modes:
v verify - does not submit the AR but prints an extensive validation report e error - rejects request if requirements cannot be fulfilled, default for qrsub
Note: Only queues where all users specified in the list have access are considered for reservation (see queue_conf(5)).
The name of the default cell, i.e. default.
$SGE_ROOT/$SGE_CELL/common/sge_ar_request global defaults file $HOME/.sge_ar_request user private defaults file
qrdel(1), qrstat(1), qsub(1), sge_types(5), checkpoint(5), complex(5), queue_conf(5), sge_pe(5), sge_resource_quota(5).
See sge_intro(1) for a full statement of rights and permissions.
2011-05-20 | SGE 8.1.3pre |