summaryrefslogtreecommitdiff
path: root/scripts/rabbitmqctl
diff options
context:
space:
mode:
authorMichael Klishin <mklishin@pivotal.io>2018-08-30 11:22:15 +0300
committerMichael Klishin <mklishin@pivotal.io>2018-08-30 11:22:15 +0300
commit62b40f7e03f9a176f5de8bd27b5795085da741c7 (patch)
tree86fef6f30700e145bc8826a9cbb436dec9d90845 /scripts/rabbitmqctl
parent606b101d1e2d8988200d013999a5348169bfd7b2 (diff)
downloadrabbitmq-server-git-62b40f7e03f9a176f5de8bd27b5795085da741c7.tar.gz
Don't error when a queue that's being deleted has no bindings to remove
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.
Diffstat (limited to 'scripts/rabbitmqctl')
0 files changed, 0 insertions, 0 deletions