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

messages: fix deadlock #3263

Merged
merged 1 commit into from
Sep 30, 2017
Merged

messages: fix deadlock #3263

merged 1 commit into from
Sep 30, 2017

Conversation

sougou
Copy link
Contributor

@sougou sougou commented Sep 30, 2017

BUG=67060474
The following deadlock is possible:

  1. runSend obtains a lock.
  2. Poller gets trigerred, and waits for lock.
  3. runSend calls this poller trigger, but the trigger will hang because
    it cannot return until poller returns.

Unfortunately, this race is not reproduceable in a test because it's
a CPU vs. CPU race. So, we just have to rely on reasoning.

BUG=67060474
The following deadlock is possible:
1. runSend obtains a lock.
2. Poller gets trigerred, and waits for lock.
3. runSend calls this poller trigger, but the trigger will hang because
   it cannot return until poller returns.

Unfortunately, this race is not reproduceable in a test because it's
a CPU vs. CPU race. So, we just have to rely on reasoning.
@alainjobart
Copy link
Contributor

alainjobart commented Sep 30, 2017

LGTM

Approved with PullApprove

@michael-berlin michael-berlin merged commit b7b65df into vitessio:master Sep 30, 2017
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.

4 participants