AWS Thinkbox Discussion Forums

Priority and job assignment seem off

So I have a job that should be picking up available slaves but isn’t. My set up is as follows:

Two groups of jobs in two Pools.

Slaves that are split into Power and Slow machines.

Pool One(with higher priority) is set to use the Power group and is picking up slaves fine.

Pool Two (with the lower priority) is set to use the Slow group but is sitting idle even though there are available slaves to use.

This just started happening when I upgraded to 6.2 Build 7.

Windows 7 OS.

Have you tried using the Job Candidate Filter?

If enabled, you can then click on a job in the job list, and the slave list will be filtered to show which slaves can pick it up. I’m guessing that something else like the job’s group, blacklist/whitelist, assigned limits, etc, are preventing it from being picked up.

Man, I need to wake up. The pool the job was using wasn’t in the list. It must have removed at some point and I completely missed it. My bad, the problem is resolved.

Thanks!

Privacy | Site terms | Cookie preferences