Back to bug 1038712

Who When What Removed Added
Perry Myers 2013-12-05 16:35:50 UTC Assignee rhos-maint eharney
Perry Myers 2013-12-05 16:36:35 UTC Depends On 1038638
Perry Myers 2013-12-05 16:36:36 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1038638
Flavio Percoco 2013-12-06 10:18:08 UTC Status NEW ON_DEV
CC fpercoco
Assignee eharney fpercoco
Link ID OpenStack gerrit 60464
Flavio Percoco 2013-12-06 13:45:58 UTC Status ON_DEV POST
Dafna Ron 2013-12-06 15:41:42 UTC CC dron
Eric Harney 2013-12-06 17:35:11 UTC Fixed In Version openstack-cinder-2013.2-7.el6ost
Eric Harney 2013-12-06 17:39:51 UTC Status POST MODIFIED
errata-xmlrpc 2013-12-06 19:36:59 UTC Status MODIFIED ON_QA
Bruce Reeler 2013-12-09 07:02:52 UTC CC breeler
Flags needinfo?(fpercoco)
Flavio Percoco 2013-12-09 09:06:03 UTC Doc Text Cause:

When the QPID broker is restarted, RPC servers attempt to re-connect. This re-connection process is not done correctly for fanout subscriptions - two subscriptions are established to the same fanout address.

Fix:

Improve the re-connection process. Ensure the topic name is present and that only one connection is established.
Flags needinfo?(fpercoco)
Don Domingo 2013-12-11 06:25:11 UTC CC ddomingo
Doc Text Cause:

When the QPID broker is restarted, RPC servers attempt to re-connect. This re-connection process is not done correctly for fanout subscriptions - two subscriptions are established to the same fanout address.

Fix:

Improve the re-connection process. Ensure the topic name is present and that only one connection is established.
When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Cinder.

With this release, QPID now creates a single queue for each topic, to be shared among all consumers of that topic. This ensures that each RPC notification is only received by a single consumer, preventing any unnecessary duplication of samples.
Don Domingo 2013-12-11 06:36:34 UTC Doc Text When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Cinder.

With this release, QPID now creates a single queue for each topic, to be shared among all consumers of that topic. This ensures that each RPC notification is only received by a single consumer, preventing any unnecessary duplication of samples.
When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Cinder.

This release removes the special-case reconnect logic that handles UUID addresses, which in turn avoids the incorrect establishment of multiple subscription to the same fanout address. The QPID broker will simply generate unique queue names automatically when clients reconnect.
Don Domingo 2013-12-11 07:11:10 UTC Doc Text When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for Cinder.

This release removes the special-case reconnect logic that handles UUID addresses, which in turn avoids the incorrect establishment of multiple subscription to the same fanout address. The QPID broker will simply generate unique queue names automatically when clients reconnect.
When the QPID broker is restarted, RPC servers attempt to re-connect. However, a bug in the QPID topic consumer re-connection logic (under the v2 topology) caused qpidd to use a malformed subscriber address after restarting.

This caused qpidd to incorrectly establish multiple subscriptions on the same fanout address after reconnecting. The QPID broker only requires one subscription; each extra subscription created duplicate RPC notification samples for individual services (e.g. Cinder).

This release removes the special-case reconnect logic that handles UUID addresses, which in turn avoids the incorrect establishment of multiple subscription to the same fanout address. The QPID broker will simply generate unique queue names automatically when clients reconnect.
Scott Lewis 2013-12-19 14:47:31 UTC Keywords TestOnly
errata-xmlrpc 2013-12-19 17:44:15 UTC Status ON_QA RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:41:27 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:41:27 UTC
Eric Harney 2013-12-23 17:49:50 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1045428
Eric Harney 2013-12-23 18:02:09 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1045428
Link ID Red Hat Bugzilla 1038712
Perry Myers 2016-04-26 14:02:46 UTC CC pmyers
Russell Bryant 2019-09-09 14:30:44 UTC CC rbryant

Back to bug 1038712