-
Notifications
You must be signed in to change notification settings - Fork 22
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
updated bunny to the latest version #56
Conversation
Using heartbeats should be fine for us. We just turned it off by default, but some clients are already using the feature. |
b0911ca
to
3dea802
Compare
The tests are green, but we need to study the interplay between the various new timeout options in the multi threaded bunny implementation. This is still WIP!!!
This reverts commit c7b4b0e.
Let's resurrect and bring this to completion. @skaes has done all the groundwork already. Thank you :) |
Ok we're taking over from here and since the last changes made here a couple of things have happened on our end that force us to speed up and also take some risks. We need heartbeats to work with publishers, as we're switching to new rabbit servers which run behind a NLB. Additionally we have to enable strict publishing timeouts to fail faster if a server isn't reachable. We will not merge this change into master but keep the 4.1 branch for that and potentially create a diverging long lived branch for follow-up changes. |
This brings updates to the heartbeat implementation which we should get in.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks gut
The tests are green, but we need to study the interplay between the
various new timeout options in the multi threaded bunny implementation.
In addition, the new bunny insists on having heartbeats enabled, which
we have turned off on our brokers.