Jump to content

Lesson Learned #306: TCP Provider, error: 2 - Connection was terminated


Recommended Posts

Guest Jose_Manuel_Jurado
Posted

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!

 

Continue reading...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...