This will stop wasting network bandwidth for monitoring.
E.g. a 200-node OpenStack installation produces aronud 10k queues and
10k channels. Doing single list_queues/list_channels in cluster in this
environment results in 27k TCP packets and around 12 megabytes of
network traffic. Given that this calls happen ~10 times a minute with 3
controllers, it results in pretty significant overhead.
Reviewed: https:/ /review. openstack. org/355477 /git.openstack. org/cgit/ openstack/ fuel-library/ commit/ ?id=b9cb86a51fc 1f6036b9fd6ef41 7dad48f705776f
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit b9cb86a51fc1f60 36b9fd6ef417dad 48f705776f
Author: Alexey Lebedeff <email address hidden>
Date: Mon Aug 22 14:30:12 2016 +0300
Monitor rabbitmq from OCF with less overhead
This will stop wasting network bandwidth for monitoring.
E.g. a 200-node OpenStack installation produces aronud 10k queues and list_channels in cluster in this
10k channels. Doing single list_queues/
environment results in 27k TCP packets and around 12 megabytes of
network traffic. Given that this calls happen ~10 times a minute with 3
controllers, it results in pretty significant overhead.
Upstream change: /github. com/rabbitmq/ rabbitmq- server/ pull/916
- https:/
To enable those features you shoud have rabbitmq containing following patches: /github. com/rabbitmq/ rabbitmq- server/ pull/883 /github. com/rabbitmq/ rabbitmq- server/ pull/911 /github. com/rabbitmq/ rabbitmq- server/ pull/915
- https:/
- https:/
- https:/
Change-Id: Icfde3360b42a84 1ad3a219b94f65a 69b2a18cea7
Closes-Bug: 1614071