I am just wondering if there is a way to re-assign nodes that are currently rendering to another job without suspending the 1st one?
Job not starting:
Since we switched to corona it seems that the job is not starting if there are still queued tasks. It this a bug/problem?
*We are rendering high res images and sometimes we need to move some nodes that are currently busy to another job that is more important and not having to wait for the 1st job to be done.
My usual way is to change the priority number on the higher priority job (higher is more important) then requeue the tasks the desired Slave is working on. This usually works unless the job has sequential rendering enabled:
Enforce Sequential Rendering : Sequential rendering forces a Slave to render the tasks of a job in order. If an earlier task is ever requeued, the Slave won’t go back to that task until it has finished the remaining tasks in order. Sequential rendering also forces the Slave to finish rendering tasks in order before switching to another job, even if that job has higher priority or this job is interruptible.
Corona jobs do not have that turned on by the submitter.
Either/or. Both work depending and @panze’s solution is helpful in situations too. For example, if you don’t want slow or broken nodes from picking up a certain job and don’t want the effort of setting up groups.
I tried to use your method but for some reason only the master node jumps to the 2nd job, the other ones jump only after the 1st job is done. I am also attaching some screenshots.
