An Azure service for ingesting, preparing, and transforming data at scale.
Executing a databricks notebook in queue for more than an hour. The cluster is up and running.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Getting a strange error since last few days. I have a lookup activity which fetch a parameter from azure SQL which is currently in serverless tier.
The timeout duration is given as 5 minutes but it still it fails,even retry of 3 doesn't work. This happens when the data factory is triggered on schedule
But if i run the same pipeline in debug mode everything works just fine.
We are having issues in live region as well where the SQL server is on a higher tier.
Can someone help?
Thanks in advance.
An Azure service for ingesting, preparing, and transforming data at scale.
Executing a databricks notebook in queue for more than an hour. The cluster is up and running.
@MartinJaffer-MSFT why does most of the activities get in Queue for very long time ?
Hi @MartinJaffer-MSFT ,
Thanks for the reply. The same published version is ran for both trigger and debug. This is happening quite frequently now a days. The lookup activity has a timeout of 5 mins and the activity is in queue for 5 minutes and it fails with timeout. We have same data factory running in multiple subscriptions and the same error happens in each suscription.
Hello @Ashish Venugopal ,
Thanks for the question and using MS Q&A platform.
I understand you are using Data Factory Lookup activity targeting Azure SQL. When you do a debug run, everything is fine, but when you do a trigger run, it times out? Can you tell me how long it takes in the debug run?
The first thing that comes to mind, is a possible difference between the version you are running debug on, and the published version. Debug runs, use whatever you see in the browser at the moment. Trigger runs use whatever was published last. Try publishing and see whether that evens things out.
We are having issues in live region as well where the SQL server is on a higher tier.
does this mean you are having two separate instances of the problem? This changes things. I do know that debug and trigger run on different computes.
Please do let me if you have any queries.
Thanks
Martin
------------------------------------------
or upvote
button whenever the information provided helps you. Original posters help the community find answers faster by identifying the correct answer. Here is how