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

Change order of tasks in connection reset #1262

Closed
wants to merge 1 commit into from

Conversation

mdellweg
Copy link

@mdellweg mdellweg commented Jan 23, 2020

This fixes a race condition, where a task can be returned an old
connection instead of waiting, while another one already started the reset.

Thanks for the analysis done by @yht804421715 and @gmbnomis .

fixes #1138

Pull Request check-list

Please make sure to review and check all of these items:

  • Does $ tox pass with this change (including linting)?
  • Does travis tests pass with this change (enable it first in your forked repo and wait for the travis build to finish)?
  • Is the new or changed code fully tested?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Please provide a description of the change here.

This fixes a race condition, where a task can be returned an old
connection instead of waiting, while another one already started the reset.

Thanks for the analysis done by @yht804421715 and @gmbnomis .

fixes redis#1138
@andymccurdy
Copy link
Contributor

This is replicated by #1270 which addresses several other thread-safety issues with the ConnectionPool.

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

Successfully merging this pull request may close these issues.

KeyError on self._in_use_connections.remove(connection)
2 participants