Skip to content

Don't error when a queue that's being deleted has no bindings left to remove on transaction retries #1689

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

Merged
merged 1 commit into from
Aug 30, 2018

Conversation

michaelklishin
Copy link
Collaborator

Proposed Changes

It can happen due to retries of (currently not guaranteed to be idempotent,
which is a separate issue in the works) binding removal. Since both
the queue and its bindings are undergoing removal, don't fail when
there's nothing left to be removed for the current transaction [attempt].

This avoids obscure and non-actionable errors in the log ({error, not_found}).
Note that the error is also not handled by the callers and ignoring them
is the only reasonable course of action that I can think of.

Types of Changes

  • Bug fix/usability (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (correction or otherwise)
  • Cosmetics (whitespace, appearance)

Checklist

  • I have read the CONTRIBUTING.md document
  • I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
  • All tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in related repositories

Further Comments

Per discussion with @dumbbell @dcorbacho @hairyhum.

It can happen due to retries of (currently not guaranteed to be idempotent,
which is a separate issue in the works) binding removal. Since both
the queue and its bindings are undergoing removal, don't fail when
there's nothing left to be removed for the current transaction [attempt].

This avoids obscure and non-actionable errors in the log ({error, not_found}).
Note that the error is also not handled by the callers and ignoring them
is the only reasonable course of action that I can think of.

Per discussion with @dumbbell @dcorbacho @hairyhum.
@michaelklishin michaelklishin added this to the 3.7.8 milestone Aug 30, 2018
@michaelklishin michaelklishin changed the title Don't error when a queue that's being deleted has no bindings to remove Don't error when a queue that's being deleted has no bindings [left] to remove Aug 30, 2018
@michaelklishin michaelklishin changed the title Don't error when a queue that's being deleted has no bindings [left] to remove Don't error when a queue that's being deleted has no bindings left to remove on transaction retries Aug 30, 2018
@michaelklishin
Copy link
Collaborator Author

Merging per discussion with @dumbbell.

@michaelklishin michaelklishin merged commit 25a3fe4 into master Aug 30, 2018
@michaelklishin michaelklishin deleted the forgiving-binding-removal-on-queue-deletion branch August 30, 2018 10:21
michaelklishin added a commit that referenced this pull request Mar 13, 2019
Since it makes direct Erlang client
connections possible.

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

Successfully merging this pull request may close these issues.

1 participant