Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feat Request] Improve the reliability of Faktory server when overloaded with connections #476

Closed
yvjessestephens opened this issue May 15, 2024 · 1 comment

Comments

@yvjessestephens
Copy link

  • Which Faktory package and version? Enterprise v1.7.0
  • Are you using an old version? Yes
  • Have you checked the changelogs to see if your issue has been fixed in a later version? Yes, it is not

Using the Enterprise version, the number of connections is capped at X number. The server allows for the number of clients connected to exceed X. If there are more than X clients connected, the behavior of the Faktory server becomes a bit unpredictable. At the very least, it stops emitting statsd metrics. It appears that the excessive number of clients connected overruns the ability of Faktory internals to connect to Redis.

Can the behavior of Faktory be improved such that when all the connections are in use that it is a little less apocalyptic?

@mperham
Copy link
Collaborator

mperham commented May 20, 2024

this is now available in 1.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants