I had our farm set up for 3 slave failures to mark a slave as bad.
However, as soon as one slave errors out on a frame, it kills all the other frames that are rendering fine and marks every task as failed.
Is this expected behaviour? How can I stop this from happening?
Rhys.
Deadline Version: 6.0.0.51480
FranticX Version: 2.0.0.51478
That’s definitely not expected behaviour of the Bad Slave Detection.
What you’re describing is how Job failure detection behaves. That is, a Job (and all its Tasks) will be marked as Failed when the total error count on that Job reaches a certain threshold. I think by default, this threshold is 100, but it sounds like someone may have accidentally set this to 1… Could you confirm whether this is/isn’t the case?
Cheers,
