Back to bug 1038718

Who When What Removed Added
Perry Myers 2013-12-05 16:40:19 UTC Depends On 1038641
Perry Myers 2013-12-05 16:40:20 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1038641
Flavio Percoco 2013-12-06 13:45:45 UTC Status NEW POST
CC fpercoco
Assignee eharney fpercoco
Dafna Ron 2013-12-06 15:41:05 UTC CC dron
Eric Harney 2013-12-06 17:35:19 UTC Fixed In Version openstack-cinder-2013.2-7.el6ost
Eric Harney 2013-12-06 17:39:55 UTC Status POST MODIFIED
errata-xmlrpc 2013-12-06 19:37:11 UTC Status MODIFIED ON_QA
Bruce Reeler 2013-12-09 06:59:21 UTC CC breeler
Flags needinfo?(eharney)
Haim 2013-12-12 12:49:56 UTC Keywords OtherQA
Flavio Percoco 2013-12-16 17:37:29 UTC Status ON_QA VERIFIED
Flavio Percoco 2013-12-17 13:59:45 UTC Doc Text A bug in the QPID topic consumer re-connection logic (under the v2 topology) incorrectly resulted in the creation of duplicate RPC notifications delivered to every subscribed consumer. As a result, samples derived from RPC notifications were duplicated to the extent that the collector service made multiple subscriptions to the topic control exchanges for individual services (e.g. nova).

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-17 23:57:59 UTC CC ddomingo
Doc Text A bug in the QPID topic consumer re-connection logic (under the v2 topology) incorrectly resulted in the creation of duplicate RPC notifications delivered to every subscribed consumer. As a result, samples derived from RPC notifications were duplicated to the extent that the collector service made multiple subscriptions to the topic control exchanges for individual services (e.g. nova).

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.

As a result, RPC requests sent to a topic with multiple servers ended up being incorrectly multicast to all servers.

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.
errata-xmlrpc 2013-12-19 17:44:27 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2013-12-20 00:43:03 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2013-12-19 19:43:03 UTC
Eric Harney 2013-12-23 14:37:11 UTC Flags needinfo?(eharney)
Eric Harney 2013-12-23 17:52:17 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1045428
Eric Harney 2013-12-23 18:02:51 UTC See Also https://bugzilla.redhat.com/show_bug.cgi?id=1045428
Link ID Red Hat Bugzilla 1038718
Perry Myers 2016-04-26 21:51:19 UTC CC pmyers
Russell Bryant 2019-09-09 16:39:13 UTC CC rbryant

Back to bug 1038718