TORQUE server parameters are specified using the qmgr command. The set subcommand is used to modify the server object. For example:
> qmgr -c 'set server default_queue=batch'
acl_hosts | |
---|---|
Format | <HOST>[,<HOST>]... or <HOST>[range] or <HOST*> where the asterisk (*) can appear anywhere in the host name |
Default | (Only the host running pbs_server may submit jobs.) |
Description |
Specifies a list of hosts from which jobs may be submitted. Hosts in the server nodes file located at $TORQUE/server_priv/nodes cannot be added to the list using the acl_hosts parameter (see Server node file configuration). To submit batch or interactive jobs (see Server configuration) through hosts that are specified in the server nodes file, use the submit_hosts parameter. Qmgr: set queue batch acl_hosts = "hostA,hostB"
In version 2.5 and later, the wildcard (*) character can appear anywhere in the host name, and ranges are supported; these specifications also work for managers and operators. Qmgr: set server acl_hosts = "galaxy*.tom.org" |
acl_host_enable | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies if the acl_hosts value is enabled. |
acl_logic_or | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies if user and group queue ACL's should be logically AND'd or logically OR'd. |
acl_roots | |
---|---|
Format | <username>@<domain> |
Default | --- |
Description | Specifies which root users are allowed to submit and run jobs. |
allow_node_submit | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies if users can submit jobs directly from any trusted compute host directly or from within batch jobs (see Configuring job submission hosts). |
allow_proxy_user | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies if users can proxy from one user to another. Proxy requests will be either validated by ruserok() or by the scheduler (see Job submission). |
clone_batch_delay | |
---|---|
Format | <INTEGER> |
Default | 1 |
Description | Specifies the delay (in seconds) between clone batches (see clone_batch_size). |
clone_batch_size | |
---|---|
Format | <INTEGER> |
Default | 256 |
Description | Job arrays are created in batches of size X. X jobs are created, and after the clone_batch_delay, X more are created. This repeats until all are created. |
cray_enabled | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies that this instance of pbs_server has Cray hardware that reports to it. See Installation Notes for Moab and TORQUE for Cray in the Moab Workload Manager documentation. |
default_queue | |
---|---|
Format | <STRING> |
Default | --- |
Description | Indicates the queue to assign to a job if no queue is explicitly specified by the submitter. |
disable_server_id_check | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description |
Makes it so the user for the job doesn't have to exist on the server. The user must still exist on all the compute nodes or the job will fail when it tries to execute. If you have disable_server_id_check set to TRUE, a user could request a group to which they do not belong. Setting VALIDATEGROUP to TRUE in the torque.cfg file prevents such a scenario (see "torque.cfg" configuration file). |
job_log_file_roll_depth | |
---|---|
Format | <INTEGER> |
Default | --- |
Description | This sets the maximum number of new log files that are kept in a day if the job_log_file_max_size parameter is set. For example, if the roll depth is set to 3, no file can roll higher than <filename.3>. If a file is already at the specified depth, such as <filename.3>, the file is deleted so it can be replaced by the incoming file roll, <filename.2>. |
job_log_keep_days | |
---|---|
Format | <INTEGER> |
Default | --- |
Description | This maintains logs for the number of days designated. If set to 4, any log file older than 4 days old is deleted. |
job_start_timeout | |
---|---|
Format | <INTEGER> |
Default | --- |
Description | Specifies the pbs_server to pbs_mom TCP socket timeout in seconds that is used when the pbs_server sends a job start to the pbs_mom. It is useful when the MOM has extra overhead involved in starting jobs. If not specified, then the tcp_timeout parameter is used. |
lock_file_update_time | |
---|---|
Format | <INTEGER> |
Default | 3 |
Description | Specifies how often (in seconds) the thread will update the lockfile. |
lock_file_check_time | |
---|---|
Format | <INTEGER> |
Default | 9 |
Description | Specifies how often (in seconds) a high availability server will check to see if it should become active. |
log_file_roll_depth | |
---|---|
Format | <INTEGER> |
Default | 1 |
Description | Controls how deep the current day log files will be rolled, if log_file_max_size is set, before they are deleted. |
log_keep_days | |
---|---|
Format | <INTEGER> |
Default | 0 |
Description | Specifies how long (in days) a server or MOM log should be kept. |
log_level | |
---|---|
Format | <INTEGER> |
Default | 0 |
Description | Specifies the pbs_server logging verbosity. Maximum value is 7. |
max_job_array_size | |
---|---|
Format | <INTEGER> |
Default | Unlimited |
Description | Sets the maximum number of jobs that can be in a single job array. |
max_slot_limit | |
---|---|
Format | <INTEGER> |
Default | Unlimited |
Description |
This is the maximum number of jobs that can run concurrently in any job array. Slot limits can be applied at submission time with qsub, or it can be modifed with qalter. qmgr -c 'set server max_slot_limit=10' No array can request a slot limit greater than 10. Any array that does not request a slot limit receives a slot limit of 10. Using the example above, slot requests greater than 10 are rejected with the message: "Requested slot limit is too large, limit is 10." |
max_threads | |
---|---|
Format | <INTEGER> |
Default | 200 |
Description | This is the maximum number of threads that should exist in the threadpool at any time. |
min_threads | |
---|---|
Format | <INTEGER> |
Default | 5 |
Description | This is the minimum number of threads that should exist in the threadpool at any time. |
moab_array_compatible | |
---|---|
Format | <BOOLEAN> |
Default | TRUE |
Description | This parameter places a hold on jobs that exceed the slot limit in a job array. When one of the active jobs is completed or deleted, one of the held jobs goes to a queued state. |
no_mail_force | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | When set to TRUE, eliminates all e-mails when mail_options (see qsub) is set to "n". The job owner won't receive e-mails when a job is deleted by a different user or a job failure occurs. If no_mail_force is unset or is FALSE, then the job owner receives e-mails when a job is deleted by a different user or a job failure occurs. |
query_other_jobs | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | Specifies whether or not non-admin users may view jobs they do not own. |
record_job_info | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | This must be set to true in order for job logging to be enabled. |
record_job_script | |
---|---|
Format | <BOOLEAN> |
Default | FALSE |
Description | If set to TRUE, this adds the contents of the script executed by a job to the log. |
resources_available | |
---|---|
Format | <STRING> |
Default | --- |
Description | Allows overriding of detected resource quantity limits (see Assigning queue resource limits). pbs_server must be restarted for changes to take effect. Also, resources_available is constrained by the smallest of queue.resources_available and the server.resources_available. |
submit_hosts | |
---|---|
Format | "<HOSTNAME>[,<HOSTNAME>]..." |
Default | --- |
Description | Indicates which hosts included in the server nodes file located at $TORQUE/server_priv/nodes (see Server node file configuration) can submit batch or interactive jobs (see Configuring job submission hosts). For more information on adding hosts that are not included in the first nodes file, see the acl_hosts parameter. |
tcp_timeout | |
---|---|
Format | <INTEGER> |
Default | 300 |
Description |
Specifies the timeout for idle TCP connections. If no communication is received by the server on the connection after the timeout, the server closes the connection. There is an exception for connections made to the server on port 15001 (default); timeout events are ignored on the server for such connections established by a client utility or scheduler.Responsibility rests with the client to close the connection first (See Large cluster considerations for additional information.). If you use Moab Workload Manager, prevent communication errors by giving tcp_timeout at least twice the value of the Moab RMPOLLINTERVAL. |
thread_idle_seconds | |
---|---|
Format | <INTEGER> |
Default | -1 |
Description | This is the number of seconds a thread can be idle in the threadpool before it is deleted. If threads should not be deleted, set to -1 (which is the default). TORQUE will always maintain at least min_threads number of threads, even if all are idle. |