This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 12%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECR%3C/text%3E%3C/svg%3E)
Hello everyone,
We have been experiencing significant queue times in Azure Data Factory for our self-hosted integration runtime (SHIR). Despite reaching out to Microsoft support for several months, we have not been able to resolve this issue. Our SHIR runs numerous processes daily for our company, and the delays are impacting our operations.
Has anyone faced similar issues or have any suggestions on how to reduce the queue time? Any insights or solutions would be greatly appreciated.
Thank you!
Can you please provide details of your flow where you are leveraging SHIR as that might help us suggest better ?
But in general terms, the simple ans would be to increse the number of nodes in your SHIR cluetr to distribute your work load or increse the tier of your server hosting the SHIR.
There can be other factors as well like network/bandwidth aspect leading to latencey in flow which in turn increases the queue time
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(288, 61%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
@Contreras,Rafael,MX-Ciudad de México
Welcome to Microsoft Q&A platform and thanks for posting your question here.
I understand that your issue with Queue time in Azure Data Factory for Self-hosted Integration Runtime Please consider the below steps and confirm us
Please refer this thread https://learn.microsoft.com/en-us/answers/questions/683418/long-queue-times-on-data-factory-shir-for-stored-p
I hope this information helps, Looking forward to your response. Thankyou.
@Contreras,Rafael,MX-Ciudad de México We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
@Contreras,Rafael,MX-Ciudad de México was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Hello, we are currently testing the scenarios that were previously mentioned. I will keep you all informed. Thank you. At the moment, we have not resolved the issue; we have only been stopping the jobs that use the most resources.
Hi Contreras,Rafael,MX-Ciudad de México ,
Did you get a chance to try the above mentioned resolution steps and see if it helped or not. Let us know if there is anything else we can help on. Thanks
Our cluster cannot grow any more in Jobs; we are at the maximum of 144 jobs per node. Even if we increase the CPU or memory, we cannot go higher.
Yesterday, the ADF generating the extra load was identified, and the pipelines were stopped.
This morning, the load is lower.
When they execute data copies, in some cases, they do not limit the number of processes that can be used, and they occupy all the cluster resources. As a result, other processes are left waiting.
We have created another cluster line called 'X' to transfer some loads.
But we need to set up something to control the consumption.
Thank you.
We are currently testing the scenarios that were previously mentioned. I will keep you all informed. Thank you. At the moment, we have not resolved the issue; we have only been stopping the jobs that use the most resources.