There doesn’t seem to be a rhyme or reason to the “Only Show slaves that can render the selected job” setting. It’ll be rendering on 5 machines but only show my local workstation as an available machine etc.
Ahhh, it’s only slaves that have both the primary && the secondary pool instead of the primary || secondary pool/
Nah that’s not it. I have 3 slaves rendering and still only 2 slaves showing up on the list of slaves that can render the job. Then I have another slave that could be rendering that’s not.
Can you provide more specifics about the job and the slaves?
For the job, this information would help:
- pool
- secondary pool (if any)
- group
- whitelist/blacklist
- any limits the job uses
If the job uses any limits:
- their names
- their whitelists/blacklists
For the slaves:
- assigned pools
- assigned groups
- if slaves can render jobs in the none pool or group
We can use this information to try and recreate the same scenario here, and then try to reproduce.
Thanks!
Ryan
Job \
User: ggreenwalt
Pool: 2d
Group: i7_v03
Limits: nuke, nuke_i
group i7_v03 members and Pool 2d:
render-i7-10
render-i7-11
render-i7-12
render-i7-13
render-i7-14
render-i7-15
limit nuke:
Slaves Excluded:
render-i7-14
render-i7-15
limit nuke-i:
Whitelisted:
render-i7-14
render-i7-15
excluded:
render-i7-10
render-i7-11
render-i7-12
render-i7-13
Visible machines:
Daedalus
render-i7-14
render-i7-15
(render i7-10 through i7-13 can render the job).
Thanks! It was the excluded slave list that was messing things up. The filter wasn’t taking this list into account, so if the limit had a white list, and a slave wasn’t on it because it was in the excluded list, it would still think that the slave couldn’t pick up the job. This will be fixed in the next beta.
Cheers,
Ryan