This post has been republished via RSS; it originally appeared at: Azure Database Support Blog articles.
In some situations, we found that our application reported the following error message: A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 2 - Connection was terminated )
Working with our customer we found that this issue might be caused when our application server reachs CPU throttling, High Memory Utilization.
Also, in AKS, High CPU Reservation (Requests) plus too many pods have very large difference between their CPU Requests and CPU Limits, these pods will be affected by CPU Throttling. To Protect the pods against CPU Throttling the recomendation is to Set their CPU Request equal to the high value of the CPU Limit, only then it will be protected because it will be using Kubernetes QOS Class Guaranteed.
Enjoy!