A large number of failedtoacquirescoreboard appear in php-fpmlog

A large number of failedtoacquirescoreboard occurs in the php-fpmlog, causing the sub-process to reach the maximum number of requests. after the kill, the new sub-process cannot be pulled, and the master process is left. The log is as follows: {code ...} after troubleshooting, when this problem occurs, I... A large number of failed to acquire scoreboard appear in the php-fpm log, causing the sub-process to reach the maximum number of requests. after the kill, the new sub-process cannot be pulled, and the master process is left.
The log is as follows:

ERROR: [pool ] no free scoreboard slotWARNING: [pool www] child 31311 said into stderr: "WARNING: failed to acquire proc scoreboard"

After troubleshooting, when this problem occurs, a 500 error occurs for a request. the 500 error occurs because the database query result set is large and this problem occurs, system log also appears

TCP: time wait bucket table overflow

Do you know why?

Reply content:

A large number of failed to acquire scoreboard appear in the php-fpm log, causing the sub-process to reach the maximum number of requests. after the kill, the new sub-process cannot be pulled, and the master process is left.
The log is as follows:

ERROR: [pool ] no free scoreboard slotWARNING: [pool www] child 31311 said into stderr: "WARNING: failed to acquire proc scoreboard"

After troubleshooting, when this problem occurs, a 500 error occurs for a request. the 500 error occurs because the database query result set is large and this problem occurs, system log also appears

TCP: time wait bucket table overflow

Do you know why?

WARNING: failed to acquire proc scoreboardIs this problem caused by the fact that the data queried by the big data result set is stored in the memory for operations and the memory of the server system is insufficient.
time wait bucket table overflowA large numberTCPThe number of connections exceeds the value configured by the system.tcp_max_tw_bucketsMaximum value.
Solution:

1. Increase system memory

2. Process the big data result set in parts or read the big database result set by row (cursor mode)

3. Modifytcp_max_tw_bucketsRelated value

The above is purely personal speculation and only for reference, because I have never encountered this error.

Check whether the script consumes a large amount of memory.