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

bz #1189480 - Rabbitmq cluster remains partitioned after short network p... #478

Merged
merged 1 commit into from
Mar 6, 2015

Conversation

jeckersb
Copy link

...artition incident

https://bugzilla.redhat.com/show_bug.cgi?id=1189480

This sets TCP_USER_TIMEOUT on all rabbitmq sockets to 5000ms. This
should allow cluster failures to be noticed quickly, as well as any
clients that might disappear on us. That allows autodelete queues to
get cleaned up earlier as well.

…k partition incident

https://bugzilla.redhat.com/show_bug.cgi?id=1189480

This sets TCP_USER_TIMEOUT on all rabbitmq sockets to 5000ms.  This
should allow cluster failures to be noticed quickly, as well as any
clients that might disappear on us.  That allows autodelete queues to
get cleaned up earlier as well.
@jguiditta
Copy link
Member

I ran through testing of this with @jeckersb adding the needed kernel patch, and it seemed to behave as desired.

jguiditta added a commit that referenced this pull request Mar 6, 2015
bz #1189480 - Rabbitmq cluster remains partitioned after short network p...
@jguiditta jguiditta merged commit 17bae4e into redhat-openstack:master Mar 6, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants