Azure App Service TCP/IP端口耗尽 [英] Azure App Service TCP/IP Port Exhaustion
问题描述
我最近收到Azure的推荐"，内容涉及达到我的App Service中TCP/IP端口的上限.
I recently got a "recommendation" from Azure regarding reaching the upper limit for TCP/IP ports in my App Service.
TCP/IP端口即将用尽您的应用服务计划已包含应用******配置为使用中等实例.托管的应用该应用服务计划正在使用4096个可用应用中的90％以上每个介质实例可用的TCP/IP端口.您可以升级实例大小以增加出站连接限制或配置连接池以更有效地使用.
TCP/IP ports near exhaustion Your app service plan containing app ****** is configured to use medium instances. The apps hosted in that App Service plan are using more than 90% of the 4096 available TCP/IP ports available per medium instance. You can upgrade the instance size to increase the outbound connection limit or configure connection pooling for more efficient use.
应用服务计划的限制(向上扩展)是否有所不同?还是可以配置我的应用服务以使用更多端口?还是为此有任何其他解决方案?
Is there a difference in Limits for App Service Plans (scale up)? or can I Configure my App Service to use more ports? Or is there any other solution for this?
一个显而易见的解决方案是向外扩展，但是由于CPU和内存使用率较低，因此我宁愿不必使用此选项.
An obvious solution would be scaling out, but since CPU and Memory usage is low I would rather not use this option if not necessarily.
作为背景，该服务是使用.Net 4.6使用ASP.NET Core MVC构建的API.
As background, the service is an API built with ASP.NET Core MVC using .Net 4.6.
推荐答案
是的，应用服务计划限制(向上扩展)存在差异:
最大连接限制如下:
每个B1/S1/P1实例1,920个连接每个B2/S2/P2实例3,968个连接每个B3/S3/P3实例有4,064个连接
1,920 connections per B1/S1/P1 instance 3,968 connections per B2/S2/P2 instance 8,064 connections per B3/S3/P3 instance
关于:其他服务(Cassandra，MSSQL，RabbitMQ等)，但我也不确定这些连接数此服务调用还将导致创建TCP连接，并且也需要计算在内.
Azure中的大多数服务都具有自己的诊断程序和Dashaboard，我们可以在进行调试时将它们关联起来，例如在我的情况下，MSSQL DTU不足以容纳并发请求的数量，因此连接正在堆积.
Most of the services in Azure are having their own Diagnostics and Dashaboard which we can correlate while doing debugging, like in my case MSSQL DTU was not sufficient to hold the number of concurrent requests and because of that the connections are piling up.
来源:
