We see many TIME_WAIT connection from edgemicro server to edgeserver. 300+ TIME_WAIT from each server. Does this 300 connections in edgemicro occupies the Max connection configuration in edgemicro.
Does anyone see issues with 300+ connection TIME WAIT from edgemicro to edge server/analytics
Would it be possible for you to verify whether these connections are created from Edge Microgateway to Edge Cloud/OPDK Deployment or to target servers of API proxies?
We could see timeout to Target servers also which is less (<100) but Time wait connections to Edgeserver is more (>300)
According to the manual page of the netstat command TIME_WAIT means following:
The socket is waiting after close to handle packets still in the network.
We could check following to troubleshoot this issue:
max_connections: (default: -1) Specifies the maximum number of simultaneous incoming connections that Edge Microgateway can receive. If this number is exceeded, the following status is returned:
res.statusCode = 429; // Too many requests
max_connections_hard: (default: -1) The maximum number of simultaneous requests that Edge Microgateway can receive before shutting down the connection. This setting is intended to thwart denial of service attacks. Typically, set it to a number larger than max_connections.
Most likely throughput at this point of time may have been high and Edge Microgateway might be still waiting for response messages from Target Servers or Token validation and/or Analytics calls made to Edge Cloud/OPDK Deployment being completed.
Thanks ecomscm, please see below response.