AWS Thinkbox Discussion Forums

beta11 job candidate filter

Assigned pools dont seem to be filtered out

Job has:

primary pool: A
secondary pool: B

With the job candidate on, machines are shown that only have the secondary pool (B) on them. I believe they would also need to be in pool A, no?

No, they don’t need to be in pool A. The way it works is that the job can be picked up by machines in pool B if there are no machines left in pool A, and if the slaves in pool B don’t have any higher priority jobs to work on. The slaves in pool B don’t need to be in pool A.

Cheers,

  • Ryan

Ok, i didnt fully think it through just looked at the tooltip of the secondary pool. This is what happens when a programmer reads english. ‘And’ becomes a logical operator :slight_smile:

“The job will only render on slaves in this pool and the primary pool”

Nevermind :slight_smile:

Privacy | Site terms | Cookie preferences