oslo.messaging

  1. Bug #1261631
  2. Comment #32

Comment 32 for bug 1261631

Revision history for this message
Openstack Gerrit (openstack-gerrit) wrote : Fix merged to oslo.messaging (master)

Reviewed: https://review.openstack.org/81962
Committed: https://git.openstack.org/cgit/openstack/oslo.messaging/commit/?id=8ae1880f7a31f6e7c985b99b2015db792d5cca46
Submitter: Jenkins
Branch: master

commit 8ae1880f7a31f6e7c985b99b2015db792d5cca46
Author: ChangBo Guo(gcb) <email address hidden>
Date: Fri Mar 21 09:49:32 2014 +0800

    Select AMQP message broker at random

    The rule of choosing AMQP message broker is that chose first
    available one in order now. The order depends on what we set in
    configuration file. That means all the connections will flock
    to same message broker and that may lead out performance issue.
    This patch randomizes the order of choosing message broker for
    each connection to leverage broker cluster.

    Change-Id: Ib5098e574d4ef81428065885e2295d0f87aba715
    Partial-Bug: #1261631