Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
Our Azure Analysis Services is in the East US 2 region and on S2 tier. We are trying to perform an auto scale-out/scale-in depending on the average QPU usage reaches a certain threshold (70-80%) for a sustained period of time. We trying to use the Azure Runbook and Powershell script to automate following the sample provided in github:
https://github.com/microsoft/Analysis-Services/tree/master/AASAutoScale
The issue we are facing is that, when the scale-out/in is occurring, regardless of whether we increase the query replicas from the Azure Portal manually or through the powershell cmdlets, the users interacting with the Power BI reports in Power BI Service suddenly get intermittent connection errors to the Azure Analysis Services. The error is as shown below:
I have tried various things, such as below, but no luck. Is there any way to get around this?
Things I have tried:
Also please let me know if I'm doing the steps correct:
Since the Sync operation is done as soon as the Process Database is complete, we don't need to perform another Sync operation as and when new Query Replicas are added or removed. Is this correct?
Please help!
Thanks!!
Hi, @Sparks
This issue may be related to Azure Service bus messaging queue. Take a try to use a higher delivery count setup for the queue. Furthermore, if the your application is mission-critical, please consider upgrade to a premium namespace: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-premium-messaging
Best Regards,
Community Support Team _ Eason
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.