Azure Batch Service showing more tasks running per node than configuration should allow

Question

I am running with this configuration:

• 1 Pool
• 2 VMs (8 cores)
• 1 Job
• 200 Tasks
• 32 Tasks per Node (what I expected to be max.)

However, I am seeing on summary in the Job overview blade that I am running more than 64 tasks. I have seen numbers ranging 64-84.

Am I missing some piece of configuration? Shouldn't this be impossible without a service request?

Thanks

Answer 1

Microsoft provided the answer to this:

Apparently tasks show as "running" when they are "preparing" or if they're actually "running." Preparing means they have been assigned to a node and they're ready to run.

https://learn.microsoft.com/en-us/azure/batch/batch-get-task-counts