oarwalltime(1)

✨ oarwalltime — the manual page, but make it make sense ✨

okay bestie, welcome to oarwalltime(1), part of the OAR commands family. this is the little guy you call when you wanna know what's up with a job's walltime, or when you wanna politely ask the OAR batch scheduler to change it. 🕐💖

---

🌸 NAME 🌸

oarwalltime — query or request a change of the walltime of a job handled by the OAR batch scheduler. that's it, that's the whole job description, and she does it flawlessly. 💅

---

🎀 SYNOPSIS 🎀

oarwalltime [options] <job_id> [<[+/-]new walltime>]

---

🦋 DESCRIPTION 🦋

so, this command manages requests to change the walltime of a job. simple concept, kinda iconic execution.

• if you give it no new walltime, it just shows you the current walltime change status for that job. like a lil status check. 👀
• if you do give it a new walltime, it requests a change of the walltime of the job — or updates a previous request you already made. no need to cancel first, she just overwrites, queen behavior.

the new walltime has to be passed in the format [+-]h:m:s. here's the tea on the signs:

• no sign → the value is a new walltime absolute value (like the one you'd pass to oarsub).
• prefixed by + → it's an increase request, bumping the walltime up by the value you passed.
• prefixed by - → it's a decrease request. shrinking the vibe.

and the cancel hack: a walltime change request that hasn't been accepted by the scheduler yet can be cancelled by passing the '+0' value. periodt. ✨

walltime changes can ONLY be requested for a running job. if it's not running, this whole thing is not gonna hit, bestie. 💀

there is no warranty that walltime can be increased, because it literally depends on the resources availability (next jobs). it's giving "we'll see if the universe says yes."

once a request is registered, it will be handled during the next pass of scheduling and granted if it fits with other jobs. so like, fingers crossed. 🫶

as per configuration — and this is the part where every site is different so listen up:

• the walltime change functionality may be disabled in your installation, and if it's not disabled, there's a maximum to the possible walltime increase.
• a walltime increase request may only be applied some time before the predicted end of the job. that apply time may be computed as a percentage of the walltime of the job.
• a walltime increase may happen incrementally, so that other scheduled jobs get more priority. that increment may also be computed as a percentage of the walltime of the job.
• the functionality may be configured differently from one queue to another. so queue A might be chill and queue B might be strict. 🧚

read your site's documentation or ask your administrator to know the configured settings. iykyk. 🌈

---

💜 OPTIONS 💜

• --force — request the walltime increase to be trialed or applied immediately, regardless of any otherwise configured delay. no waiting around, main character energy.
• --whole — request the walltime increase to be trialed or applied wholly at once, or not applied otherwise. all or nothing, basically.
• --delay-next-jobs — request the walltime increase to possibly delay next batch jobs (but not advance reservations), if required to fit in the resources allocation.

Warning: this implies delaying any other batch jobs, including the ones from other users. using this option may be prohibited. so like, check with your admin before you go delaying other people's stuff, fr fr. 😭

• --timeout — specify a timeout (in seconds) after which the walltime change request will be aborted if not already accepted by the scheduler. by default, there is no timeout, unless a default timeout is set by the administrator.
• -h, --help — print help command message. the classic. 💖
• -V, --version — print OAR version.

---

👑 NOTES 👑

• all changes are logged. and changes using the force or delay-next-jobs options are accounted. so yes, the receipts exist. 📝
• please mind the walltime of the job and do not rely too much on that functionality. it's a feature, not a personality trait.
• the shell environment variables of the job are not updated: OAR_JOB_WALLTIME, OAR_JOB_WALLTIME_SECONDS. so don't go reading them and expecting fresh info, bestie.
• walltime change events for a job are listed in the oarstat output. that's where you go snooping. 🔍

---

🍓 SEE ALSO 🍓

oarstat(1), oarsub(1), oardel(1)

---

🌟 COPYRIGHTS 🌟

Copyright 2003-2017 Laboratoire d'Informatique de Grenoble (http://www.liglab.fr). This software is licensed under the GNU General Public License Version 2 or above. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

---

and that's the whole page, gorgeous. 💖 this was oarwalltime, page 1, from the OAR commands collection, dated 2025-03-24. go forth and manage those walltimes responsibly. mwah. 💅✨🎀