I’ve got my job scheduling set to priority_date_pool. Most of the jobs I submit are 3dsmax and so are in the same pool and jobs seemed to respect priority. However I just started submitting commandline jobs to it. I told it to do one with a priority of 100 so it should have started right away. Except it didn’t. So I figured I’d restart a slave to force the issue. Only it started back on the 3dsmax job instead of taking the commandline job. So I thought perhaps I’ve got priority backwards by mistake and 0 is highest (like backburner), nope that’s not it. The only way I could get it to start was to suspend all the 3ds max jobs. It seems that despite priority being first in the list…the pool is still taking precedence.
That’s really strange… After some testing I can’t seem to reproduce this issue. Perhaps the setting’s not getting set properly? Can you check the “networkSettings.xml” file in the "\your\repository\settings"folder. Look for the “” line and make sure it is being set to Priority_Date_Pool. Also check to make sure the 3dsmax job’s priority isn’t also set to 100.
-Cody
Now this is really odd. Yesterday priority wasn’t working correctly. Today no problem. Its possible in my fiddling I accidently fixed the issue, but I had thought I had left it they way it originally was found. So for the moment everything is fine…if it crops up again I may be back.