titan

Up since 11/8/17 02:45 pm

eos

Up since 11/14/17 11:20 pm

rhea

Up since 10/17/17 05:40 pm

hpss

Up since 11/20/17 09:15 am

atlas1

Up since 11/15/17 07:25 am

atlas2

Up since 11/27/17 10:45 am
OLCF User Assistance Center

Can't find the information you need below? Need advice from a real person? We're here to help.

OLCF support consultants are available to respond to your emails and phone calls from 9:00 a.m. to 5:00 p.m. EST, Monday through Friday, exclusive of holidays. Emails received outside of regular support hours will be addressed the next business day.

Titan Batch Queues

See this article in context within the following user guides: Titan

Queues are used by the batch scheduler to aid in the organization of jobs. Users typically have access to multiple queues, and each queue may allow different job limits and have different priorities. Unless otherwise notified, users have access to the following queues on Titan:

Name Usage Description Limits
batch No explicit request required Default; most production work runs in this queue. See the Titan Scheduling Policy for details.
killable #PBS -q killable Opportunistic; jobs start even if they will not complete before the onset of a scheduled outage.
debug #PBS -q debug Quick-turnaround; short jobs for software development, testing, and debugging.
The batch Queue

The batch queue is the default queue for production work on Titan. Most work on Titan is handled through this queue.

The killable Queue

At the start of a scheduled system outage, a queue reservation is used to ensure that no jobs are running. In the batch queue, the scheduler will not start a job if it expects that the job would not complete (based on the job’s user-specified max walltime) before the reservation’s start time. In contrast, the killable queue allows the scheduler to start a job even if it will not complete before a scheduled reservation.

Note: If your job can perform usable work in a (1) hour timeframe and is tolerant of abrupt termination, this queue may allow you to take advantage of idle resources availalable prior to a scheduled outage.
The debug Queue

The debug queue is intended to provide faster turnaround times for the code development, testing, and debugging cycle. For example, interactive parallel work is an ideal use for the debug queue.

Warning: Users who misuse the debug queue may have further access to the queue denied.

More detailed information on any of the batch scheduler queues can be found on the Titan Scheduling Policy page.