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

Do not restart RabbitMQ for Policy Change #445

merged 1 commit into from May 14, 2017


None yet
3 participants
Copy link

commented May 14, 2017

Addresses #441

We don't have to restart RabbitMQ to apply policies.

The changes in #425 will cause these notifications to fire on every Chef run.

Straight from

Policies can change at any time. 
When a policy definition is updated, its effect on matching exchanges and queues will be reapplied.
Usually it happens instantaneously but for very busy queues can take a bit of time (say, a few seconds).
Do not restart RabbitMQ for Policy Change
The RabbitMQ documentation states that policy changes are applied in real-time

This comment has been minimized.

Copy link

commented May 14, 2017

@jjasghar LGTM. Should I merge?

@jjasghar jjasghar merged commit 0e031f4 into rabbitmq:master May 14, 2017

1 check failed

continuous-integration/travis-ci/pr The Travis CI build could not complete due to an error

This comment has been minimized.

Copy link

commented May 14, 2017

I'll release a new version soon. I'm going to revisit the PRs and ideally get a new release cut on the 18th.


This comment has been minimized.

Copy link
Contributor Author

commented May 14, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.