Understanding Gateway Clusters in Microsoft Fabric

Concerned about high availability of your On-Premises Data Gateway within Microsoft Fabric? Gateway clusters are a way of ensuring you can process data for sources going through a gateway.
What is an on-premises data gateway?
learn.microsoft.com/data-inte...
On-premises data gateway architecture
learn.microsoft.com/data-inte...
Manage on-premises data gateway high-availability clusters and load balancing
learn.microsoft.com/data-inte...
Plan, scale, and maintain a business-critical gateway solution
learn.microsoft.com/en-us/dat...
📢 Become a member: guyinacu.be/membership
*******************
Want to take your Power BI skills to the next level? We have training courses available to help you with your journey.
🎓 Guy in a Cube courses: guyinacu.be/courses
*******************
LET'S CONNECT!
*******************
-- / guyinacube
-- / awsaxton
-- / patrickdba
-- / guyinacube
-- / guyinacube
-- guyinacube.com
**Gear**
🛠 Check out my Tools page - guyinacube.com/tools/
#MicrosoftFabric #Gateway #GuyInACube

[@tlanza89]

I would love a video on how to set which gateway should be the primary in a cluster!

[@RichardOliver]

Our nodes in a cluster are reporting different version numbers, bizarrely, despite both being updated each time (currently 3000.222.5 and 3000.186.18).

[@davidcousins8407]

Yep, been like that for a while. If you login to the gateway it sometimes triggers the service to realise that you have indeed updated it.

[@bertholdflikkema8599]

Q: the gateway cluster can also be used in fabric datafactory right? What I'm curious about is how the concurrency settings of the gateway in fabric datafactory (assuming those exist, same as in azure datafactory) relate to concurrency settings inside pipelines. For example, let's say your gateway is configured to handle 5 concurrent jobs, one pipeline that uses the gateway has 10 concurrent activities, does that mean 5 activities will have to wait? (Assuming the server the gateway is installed on is having an easy time and is not the bottleneck) In other words; does the number of concurrent jobs relate to the number of concurrent pipeline runs or to the number of concurrent activity runs? MS documentation for the shelf hosted integration runtime is not clear on this. And also, how should the number of concurrent jobs be set in relation to the processors/threads of the machine(s) it is installed on.