Job Dependencies not working properly?

Deadline
1

The Job Dependencies have been reworked in the latest version of Deadline (1.2.15710). Now, the Slaves periodically scan the repository for dependent jobs that need to be resumed. This is also how jobs that are set to be deleted upon completion are handled.

There is a setting in the Repository Options in the Monitor called "ScanJobRepositoryPercentage" which detemines how often the Slaves perform this scan. Unfortunately, the code for this percentage is backwards, so setting it to 100% means the slaves rarely will perform the scan, and setting it to 1% means the slaves will almost always perform the scan.

If dependent jobs aren't being resumed as fast as you would like them to, try lowering the percentage (in this case). The fix for this will be included in a future release.

Please let the deadline support team know if you run into any other problems regarding Job Dependencies.

Kind regards,
 - Ryan

2

It’s good to know that the percentage is reverse. Is it the same thing for all percentage value in the repository setups? (DequeueBadJobPercentage and ScanJobDropsPercentage)


3

Only the ScanJobRepositoryPercentage setting is reversed. The other two

work properly.

4

Another issue has been found regarding job dependencies not working. In the Repository Options, the ScanJobDropsPercentage cannot be zero. 25-50% would likely be a good setting.

5

One question on the new behaviour. What would happen in this situation:



Say, the dependent job starts rendering (as the one it depended on

finished already), but it’s not rendering what the artist expected, so

gets suspended. Would it randomly keep resuming when a slave notices

that it’s suspended?





cheers,

laszlo

6

Yes, the job would keep resuming. You would have to remove the

dependency from that job before suspending it.

7

Hi Ryan.



I had reports from one of my user that the dependency didn’t worked with the new version in one case.



My ScanJobRepositoryPercentage is set to 10.



I will ask them to perform more test with dependencies and report any failed dependency jobs here.



Thanks

8

Just to report that a second user reported a denpendency not working.



Thnaks

9

Hi Sylvain,



It should be noted that the dependencies are not instant anymore like

they used to be, and the chances of a dependent job being resumed are

based on the percentages you specify in the repository options. It is

also possible that a job may be locked for some reason, and that would

prevent the dependent job from being resumed until the lock is released

(this was the main reason we modified the dependencies in the first place).



Try maxing out the percentages in the repository options to see if you

still have dependency problems. Due to the “Reverse Percentage Order”

bug, that would be:



ScanJobDropsPercentage = 100

ScanJobRepositoryPercentage = 1



I know, it’s confusing, but the bug has been fixed for the next release. :slight_smile:



Kind regards,

  • Ryan
10

Thanks Ryan, I will try that and let you know