Hi,
we have sometimes some MaxTime failures in our rush queue and the frames are then killed after MaxTime is reached. This is fine but still every frame is rendered, reaches MaxTime and is finally killed.
We would like to monitor a job and if more then, let's say 5 frames,
are killed due to Maxtime the job (or a series of jobs) should be skipped completely and no more frames should be renderered.
Because we usually chain several jobs together with the WaitFor command,
a single jobs with 100 frames reaching MaxTime blocks the renderfarm for several hours which is mostly a problem at night when the farm is not watched.
A solution would be to have something like a TimeOutCommand, that
calls a script that can take appropriate action (This would be on a per frame basis), or even better a general StatusCommand that could be called for every frame, or for every job and additional information could be passed via environment variables.
Since the killing of the process is initiated by rush, my custom render
script can not detect that it was killed because it reached MaxTime.
The only solution i can think of right now is to go through every job in
the queue and parse the log files if there is any MAXTIME entry.
Am i missing something here or what would be the best approach for this problem?
Cheers,
Lutz Paelike
Pipeline Supervisor
D-Facto-Motion GmbH
|