Forum Discussion

anttijarvinen's avatar
anttijarvinen
Frequent Visitor
2 years ago
Solved

On-premises gateway throttling issue

Hi,

 

I encountered a problem while testing load balancing with two on-premises gateways, with the other instance throttled.

 

Following these instructions https://learn.microsoft.com/en-us/data-integration/gateway/service-gateway-high-availability-clusters#load-balance-based-on-cpu-and-memory-limits , I throttled one of the instances with MemoryUtilizationPercentageThreshold = 30 . This is under the normal memory consumption of the instance, and should (to my understanding) always "guide" refreshes to the other machine without throttling.

 

However, this led to the on-demand refresh of an example dataset to always fail, with an error message "DM_GWPipeline_Gateway_GatewayOverloadedMemory".

 

Have I understood something wrong about the load balancing and throttling?

 

Thank you

Antti

 

  • lbendlin's avatar
    lbendlin
    2 years ago

    Why are you torturing the VM? Gateway cluster members should have at least 16GB, but better 32GB. 8GB will always lead to memory starvation.

7 Replies

  • Your mashup workloads still need to fit into memory.  How much is 30% in actual MB ?

    • anttijarvinen's avatar
      anttijarvinen
      Frequent Visitor

      It's 0,3x8GiB=2,4GiB

      Idle memory consumption is in 40%.

      -> I wanted to have queries always "fail" in this instance.

      • lbendlin's avatar
        lbendlin
        Icon for Super User rankSuper User

        Why are you torturing the VM? Gateway cluster members should have at least 16GB, but better 32GB. 8GB will always lead to memory starvation.