AWS Thinkbox Discussion Forums

Slave takes 1.5+ minutes to dequeue a task?

2017-11-20 11:39:04: Performing pending job scan 2017-11-20 11:39:04: Pending Job Scan - Loading pending and active jobs 2017-11-20 11:39:04: Pending Job Scan - Loaded 1 pending and active jobs in 1.388 ms 2017-11-20 11:39:04: Pending Job Scan - Scanning pending and active jobs 2017-11-20 11:39:04: Pending Job Scan - Released 0 pending jobs and 0 pending tasks in 13.000 μs 2017-11-20 11:39:04: Pending Job Scan - Done. 2017-11-20 11:39:04: Processing Pending Job Events 2017-11-20 11:39:04: Pending Job Events - Checking for pending job events... 2017-11-20 11:39:04: Pending Job Events - Processing 0 job events 2017-11-20 11:39:04: Pending Job Events - No more job events to process 2017-11-20 11:39:04: Pending Job Events - Done. 2017-11-20 11:39:04: Skipping repository repair because it is not required at this time 2017-11-20 11:39:04: Skipping house cleaning because it is not required at this time 2017-11-20 11:41:23: CheckPathMapping: Swapped "\\windows\path\to\script" with "/mac/path/to/script"

As shown above, the slave sits (it’s the only active slave on the farm ATM) for over two minutes before it finds the next task (the job has several tasks with “Queued” status ready and waiting). What setting am I missing?

Hello!

What version of Deadline are you running? I want to see if there are any bugs in the version you are running. When the job is sitting queued what is the slaves status?

Regards,

Charles

Deadline 10.0.6.3, and the slave sits Idle.

Privacy | Site terms | Cookie preferences