CONDOR_RESCHEDULE(1)

💖 condor_reschedule 💖

okay bestie, this is a page from the HTCondor Manual — yes, the actual HTCondor docs, and yes, we're doing this together, hand in hand, no cap. 🫶

✨ NAME ✨

condor_reschedule — update scheduling information to the central manager 💅

---

🌸 SYNOPSIS 🌸

condor_reschedule [-help | -version ]

condor_reschedule [-debug ] [-pool centralmanagerhostname[:portnumber]]
[ -name hostname | hostname | -addr "<a.b.c.d:port>" | "<a.b.c.d:port>"
| -constraint expression | -all ]

---

🦋 DESCRIPTION 🦋

so basically condor_reschedule updates the info about a set of machines' resources and jobs to the central manager. that's the whole vibe. 📡

the way this is useful: you use it to force an update before you go look at the current status of a machine. and how do you look at the status of a machine? with the condor_status command. cute, right? 💖

condor_reschedule also kicks off a new negotiation cycle between resource owners and resource providers on the central managers, so jobs can get matched with machines right away. iconic. this slaps in situations where the time between negotiation cycles is kind of long and an administrator wants to see if a job in the queue will get matched without waiting around for the next negotiation cycle. ⏳✨

⚠️ but listen — a new negotiation cycle cannot occur more frequently than every 20 seconds. if you ask for a new negotiation cycle inside that 20 second window, your request gets deferred until 20 seconds have passed since that last cycle. the gate is real, bestie. 🚧

---

🎀 OPTIONS 🎀

• -help — display usage information 👀
• -version — display version information ⭐
• -debug — causes debugging information to be sent to stderr, based on the value of the configuration variable TOOL_DEBUG 🐛
• -pool centralmanagerhostname[:portnumber] — specify a pool by giving the central manager's host name and an optional port number 🌊
• -name hostname — send the command to a machine identified by hostname 📛
• hostname — send the command to a machine identified by hostname 📛
• -addr "<a.b.c.d:port>" — send the command to a machine's master located at "<a.b.c.d:port>" 🏠
• "<a.b.c.d:port>" — send the command to a machine located at "<a.b.c.d:port>" 🏠
• -constraint expression — apply this command only to machines matching the given ClassAd expression 🎯
• -all — send the command to all machines in the pool 🫂

---

🔥 EXIT STATUS 🔥

condor_reschedule will exit with a status value of 0 (zero) upon success, and it will exit with the value 1 (one) upon failure. so like... zero = slay, one = not slay. 😭

---

🌈 EXAMPLES 🌈

want to update the information on three named machines? say less:

$ condor_reschedule robin cardinal bluejay

to reschedule on a machine within a pool other than the local pool, use the -pool option. the argument is the name of the central manager for the pool. 🗺️

🚨 note that one or more machines within the pool must be specified as the targets for the command. don't skip that part, bestie.

this next one reschedules the single machine named cae17 within the pool of machines that has condor.cae.wisc.edu as its central manager:

$ condor_reschedule -pool condor.cae.wisc.edu -name cae17

---

💜 AUTHOR 💜

HTCondor Team 👑

---

🌟 COPYRIGHT 🌟

1990-2026, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0. 📜

---

and that's the whole page, bestie!! 🎉 this was HTCondor Manual material, footer said Oct 16, 2026 and everything — go forth and reschedule, you absolute queen. 👑✨💖