Maya Submission Script Problem - Priority

Deadline
1

Hello,

when submitting a job from within Maya2011 via the provided submission script I set the priority to e.g. 80 but it always gets submitted with priority 50.
I know this is a minor bug, but I wanted to mention it anyways.

Or maybe it´s not a bug, but an option set wrong by myself? :wink:

2

We were able to reproduce this problem, and after checking the code for the script, it’s obvious what the bug is. What’s really strange is that this hasn’t come up before in previous Maya versions, so I’m guessing something changed in 2011 that caused this bug to show its face.

We’ll be sure to get this fixed for the next release, which should be out at the beginning of August.

Thanks for reporting this bug!

  • Ryan
3

Hello Ryan,

I installed Deadline 4.1, but the issue is still there. So it wasn´t fix for this update I guess?
greetings
andy

4

Hi Andy,

It was fixed for this update. When you installed 4.1, did you upgrade the clients and the repository, or just the clients? The updated maya script would have been included in the repository upgrade.

Cheers,

  • Ryan
5

hey,

oh i upgraded the repository as well as the slaves, but didn´t use the new submission script :slight_smile:
thanks Ryan!

Have a nice weekend!
greetings
andy

6

Me again…sooorry…

Job gets submitted with defined priority etc. works fine!
but here´s an example…
slaves a+b are running and working on job1 with priority 93
Then I submit a new job2 with priority 95…
I start slave c which begins working on job2 as it should.

Slaves a+b finish their current tasks from job1, but after that they don´t grab a task from job2 (prio95), but will take the next task from job1 (prio93) instead.
Is this intended?
Or is there an option to change this behavior?

thanks in advance!

7

That’s not the intended behavior. All things being equal, slaves a+b should move on to job2. I just tested your example here, and everything worked as expected.

A couple of things to check:

  1. Is job2 being submitted to a different pool than job1?
  2. Is job2 using a machine limit, or a whitelist/blacklist?
  3. Is job2 using any limit groups?
  4. Does job2 have any errors (specifically, errors from previous attempts from slave a or b)?
  5. In the Repository Options, what is your Job Scheduling Order in the Scheduling Settings set to?

Cheers,

  • Ryan
8

Hello again,

  1. no pools are defined
  2. no limit no white-/blacklist
  3. no limit groups used in the jobs
  4. no the jobs render fine
  5. Priority_Pool_Date

In addition when submitting a maya job with 6 layers e.g. it happens that each machine grabs a different job or 2 machines work on one job and 4 machines on the remaining (all the same priority)
in the past versions I never had these problems.
All machines started to work on the same job even if some jobs had the same priority.

9

I have a feeling this is related to the problem you’re having here:
viewtopic.php?f=11&t=4134&start=0

If the slave can’t reliably “see” all the jobs in the repository, it would definitely explain why things are picked up out of order.

Cheers,

  • Ryan