Yeah, I enabled it at
submission, and I verified it
was checked in the job
properties.
It only has the problem if it
encounters an error, but in
this case the error was it not
finding the FlexLM server, so
it would have been best for it
to just re-try the same frame.
Wow, that is helpful info!
We should tweak the behavior of licenses on Deadline - if the machine cannot find a license, it should retry N times before failing the job…
Thanks!
I’m terrible at detecting sarcasm in text.
- Chad
I’m terrible at detecting
sarcasm in text.
Probably because there was no sarcasm in the text?
I was really happy you gave us the reason for the job failing, because we are trying to tweak the way licenses are managed (for example, if you launch Beta 18 without a license, it will remember there was none and will NOT attempt to acquire a license until you restart Max, thus enabling people to use the Evaluation Mode without constant license windows popping up).
In the case of Deadline, we are probably failing a job the moment a license cannot be found, but the reason for the missing license could be overloaded network, so we should probably persist and try multiple times before failing the job, thus avoiding the dropping of the frame.
So knowing that you actually got failing frames because of missing licenses was VALUABLE info and I thanked you for it.
I shouldn’t have used WOW in the beginning though…
Believe it or not, we are taking this stuff very seriously - Siggraph is only 3 weeks away!
Chad,
In Beta 18, we actually changed the Deadline licensing behavior of Krakatoa, too. If a slave picks up a partitioning job and acquires a license once, it will hold that license until it finishes or fails. Thus, going to the next task should cause no new license request - this should apply to both Deadline partitioning modes and even the local partitioning mode (which used to ask for a license on each frame in Beta 17).
If you were using Beta 18 when you hit the license problem, we would like to know about it as it could be a bug.
If you were using Beta 17, it was sort of as expected.
Yes, it was beta 18, but unfortunately, I removed the job. I’ll watch more carefully to see if it fails again with a license error without prior failure for another reason.