ProxySG stopped process requests - Maximum concurrent HTTP client worker limit reached

book

Article ID: 241933

calendar_today

Updated On:

Products

ISG Proxy

Issue/Introduction

ProxySG stopped process requests - Maximum concurrent HTTP client worker limit reached

Environment

Release : 7.3.7.1

Component :

Resolution

Having investigated the logs, we see the below.

We see that on the day of the reported appliance non-response to traffic, at 14:00 hours, the client volume peaked at 2550, surpassing the designed max. of 2500 for the appliance model. The client refers to the maximum concurrent HTTP connections that the appliance can receive and process. Above the designed max., the appliance would stop processing web requests further. The client volume is synonymous with the load or the volume of web requests.

We also see that immediately after the max. limit was reached, for the concurrent HTTP connection, the appliance went into memory "regulation" when memory pressure exceeds 80%. Regulation means that the ProxySG will no longer accept new connections until it can finish processing current requests and free resources. When a ProxySG goes into regulation, all users utilizing that proxy may experience extremely slow Internet access, or may not get any response at all, until the regulation is cleared.

Upon reaching the TCP regulation state the proxy physically shuts down incoming TCP connections, to alleviate the memory state that is occurring. By stopping new traffic coming to the ProxySG, it has time to deal with what is currently in memory. Hopefully, memory use will then be reduced. When we hit the lower limit, in this case, 75%, the ProxySG begins accepting new connections again.

Ref. doc.: https://knowledge.broadcom.com/external/article/167211/what-does-memory-pressure-mean-in-the-pr.html

Attachments