This PR is stale because it has been open for 30 days with no activity.

It seems that a long time has passed, can someone help to review it?

Curious about the state of this PR, ran into a similar issue recently.

This may become a bigger problem as cpu's get more and more cores. I can't really think of a more complete solution than informing users via the documentation that ConnectionRefused may occur if the backlog fills up, and allowing them to increase it (to within the system limit).
I encountered this question on SO: https://stackoverflow.com/q/77042910/3220135 where the user solved the problem by polling the client side until the connection was not refused which worked for them, but I don't think is a general solution, and still requires editing the multiprocessing library.

Hi! I hope this change gets in soon, as I'm running in a high end system and facing this issue a lot.

Any updates on this? Can this be taken up? @junnplus

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

Most changes to Python require a NEWS entry. Add one using the blurb_it web app or the blurb command-line tool.

If this change has little impact on Python users, wait for a maintainer to apply the skip news label instead.

This PR is stale because it has been open for 30 days with no activity.