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

possible accept_new_conns() bug #43

Closed
GoogleCodeExporter opened this issue Jul 15, 2015 · 1 comment
Closed

possible accept_new_conns() bug #43

GoogleCodeExporter opened this issue Jul 15, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link
Contributor

Just from eyeballing the code, I think the accept_new_conns() function (new
connection throttling) might not work.

accept_new_conns(false) is called by the listen thread when there aren't
enough file descriptors.  Later, in conn_close(), the code calls
accept_new_conns(true) since closing a connection releases a file descriptor.

But, there's a sanity check in accept_new_conns(), line 3079...

    if (! is_listen_thread())
        return;

I haven't written a test or proven it live, but I think that
accept_new_conns(true) never really works because of that check.  Meaning
once memcached stops accepting new connections, it never starts accepting
new connections anymore.

Original issue reported on code.google.com by steve....@gmail.com on 10 Apr 2009 at 8:45

@GoogleCodeExporter
Copy link
Contributor Author

This is fixed in 1.2.8 and dev

Original comment by dsalli...@gmail.com on 14 Apr 2009 at 7:20

  • Changed state: Fixed

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

No branches or pull requests

1 participant