Hi,
I am bit new to PBS, Need some help in this.
I require to reserve some resources within a normal queue by a user to run priority job at some scheduled time. Also we have node binding configuration in pbs, can some one help how to do it, i mean what changes (in job submission/configuration ) required step by step.
PBS documents says, Advance / standing reservation can be done if nodes are not binded with queues, i.e nodes should not be assigned to any queue.
Node to queue mapping is not recommended and is not efficient in terms of resource usage by the end users. It is recommended to configure Qlists instead.
I have tried the above procedure, which successfully created a new reservation queue reserving nodes from queue “queue1”.
Now the thing is, Advance reservation creates a new name queue (ex: R12345) which should be mentioned in job script (PBS -q R12345) while submitting the job.
Moving further…
Can we customize “reservation queue-name” (like R12345 --> My_Resv_Q) ?
Is there any option to use reserved nodes from reservation queue(R12345) as normal, when no priority job is running.
Suppose a job is running in Reserved Time slot in reserved queue, let say JobA running in R12345. If we require to submit a more priority JobB in R12345, what will happen ? how can we acheive JObB to run immediately,if we can afford JObA to hold.
Please suggest the possibilities.
**** Just enjoying playing with PBS & exploring the new possibilities ****
No, the queue name is created dynamically based on reservation confirmation
Short answer is NO, when the reservation is ACTIVE.
If you see when the reservation is confirmed, the nodes are kind of mapped to the Reservation queue.
You can check that by running pbsnodes -av | grep -i resv , you will see something like below
resv = R11257.servername , these are the nodes that belong to respective reservation queue.
The reservation is created to run priority jobs with a walltime . The reservation is created to expect resource available by the workload you would have at that time.
Any jobs can be submitted or queue moved to RESERVATION queue. The reservation nodes are available to all the queues before the RESERVATION start-time. Please note walltime plays a crucial role when using reservation and submitting jobs to other queues before the reservation start time.
The basics of reservation is to reserve compute resources for a specified amount of time (guarantied) for a specific priority workload ( jobs ) .
There might be many ways:
job_sort_formula - with special priority ( this special priority can be bumped up using qalter )
suspend JobA
if JobA is queued, you can qhld jobA
delete JobA
Please check 4.9.21.12 Examples of Using Resource Permissions in Job Sorting
Formula in the PBS Professional 19.2 Administrator’s Guide. Page: AG-155
If you build from source, look at the code bracketed by comments with “localmod 075”. This is a NAS localmod that allows you to assign names to reservations that can then be used when submitting jobs.
There is a limitation to this code: multiple reservations can have the same name. It is unspecified which reservation will be picked. In practice here, this has not been a problem and is sometimes a feature.
yeh, i have found the same,
But It was a reply to Dale’s suggested Example above.
There Resv ID can be assigned with names that can then be used when submitting jobs.
Sorry to be so slow to respond. The pbs_rstat -f output shows that the name got recorded. So, the problem is somewhere in the pbs_rstat code that displays things. I recall making some changes in our part of that code for pbspro 19. You can find these changes (and others) via:
git clone https://github.com/drtoss/pbspro.git drtoss19
cd drtoss19
git checkout nas_mods