commit 512c0e43efa2748d26556214ee59b86f2b4b061d
Author: Russell Bryant <email address hidden>
Date: Thu Jun 12 16:13:58 2014 -0400
Qpid: advance thru the list of brokers on reconnect
Sync 877f1cab328fe8a9f8214687ea7e1287862de87d from oslo-incubator's
stable/havana branch.
In Qpid implementation, when using multiple qpid_hosts, we don't want to
immediately retry failed connection for the same failed broker. This was not
the case in existing implementation though, where we've always attempted to
reconnect starting from the first broker in the list of candidates. So if the
first broker failed, we initiated reconnect to the same failed broker.
This change makes reconnect() implementation to select the next broker in the
list. This also means that non-failure reconnect attempts will also switch the
current broker. All in all, users should not rely on any particular order to
use brokers from the list, so this should not constitute an issue.
Reviewed: https:/ /review. openstack. org/99754 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=512c0e43efa 2748d26556214ee 59b86f2b4b061d
Committed: https:/
Submitter: Jenkins
Branch: stable/havana
commit 512c0e43efa2748 d26556214ee59b8 6f2b4b061d
Author: Russell Bryant <email address hidden>
Date: Thu Jun 12 16:13:58 2014 -0400
Qpid: advance thru the list of brokers on reconnect
Sync 877f1cab328fe8a 9f8214687ea7e12 87862de87d from oslo-incubator's
stable/havana branch.
In Qpid implementation, when using multiple qpid_hosts, we don't want to
immediately retry failed connection for the same failed broker. This was not
the case in existing implementation though, where we've always attempted to
reconnect starting from the first broker in the list of candidates. So if the
first broker failed, we initiated reconnect to the same failed broker.
This change makes reconnect() implementation to select the next broker in the
list. This also means that non-failure reconnect attempts will also switch the
current broker. All in all, users should not rely on any particular order to
use brokers from the list, so this should not constitute an issue.
Change-Id: Ia148baa6e1ec63 2789ac3621c8517 3c2c16f3918
Partial-Bug: 1261631