Comment 3 for bug 1279594

Because of the way we have rabbit configured in haproxy this issue will bring down the entire cluster. The way we have haproxy configured is that the primary controller is the only active member and the others are backups. When rabbit runs out of file descriptors it will still accept connections but it can't actually do anything with them. This means that haproxy will never think the node is down and will continue to funnel all connections to the primary controller. Eventually none of the OpenStack services can talk to rabbit and the entire cluster stops working.