We have our render farm set up with a draft plugin to create Draft jobs that render videos and upload them to Shotgun when the initial job has rendered out the frames.

Recently we set up a new more powerful machine that has been set up with 6 slave instances running concurrently. We noticed that more often there were jobs that finished without actually creating the draft jobs, and when I looked at the post job reports, I saw while:

It looks like they're all just using the same file name, so if multiple instances on the same machine try to run at the same time then they clash because they obvious can't overwrite the file while another machine is using it.

We're still on Deadline 7.2 so I don't know if this has been fixed in later releases, but I thought I should flag it before I look through for a way to solve it myself.

eamsler wrote:It doesn't look like it has actually. I'll log that as an issue. We'll just need to change the call to GetDeadlineTempPath() use something a bit more random.

Thanks! Out of curiosity, how do you plan to do that? Just because I imagine you'd want to avoid it being totally random and having a series of files created that never gets cleared out. I initially thought that basing it off the slave name would be a good idea, but it didn't seem to be as easily accessible as I hoped so we're opting to just incrementing numbers when a file write fails. This way it'll still overwrite jobfilename.job and jobfilename_1.job, without creating many files left on the folder.