Are task error limit changes applied to running tasks?

Deadline
1

One of our producers just pointed out what sounds like potential bug. Some jobs were submitted with our default Task Error Limit of 4, and he overrode that limit on the jobs after the fact to set the limit to 1. However, according to him, tasks that were rendering already when the limit was changed did not respect the new value of the job-level override, and would thus be re-queued at least once after hitting an error.

I wanted to run it by you guys to get confirmation on what the existing behavior is (or should be), and to see if there’s any possibility this could be a bug.

Thanks.

2

Hello,

I am pretty sure that changes to job properties generally required a suspend and requeue of the job in order for slaves to pick the changes up. I’ll check with the devs in the morning to be sure, and to see if the process has changed since the last time I looked at it. Thanks.

3

Hey Nathan,

The problem is that the slaves don’t check if the job has changed when determining if the task should be marked as failed or not. We’ll get this fixed in 7.1.

Cheers,
Ryan

4

Great, thanks Ryan.