Notification - when no listenere without pool exist the notification queue is not consumed

Bug #1814544 reported by Harald Jensås on 2019-02-04
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ken Giusti

Bug Description

The oslo messaging documentation[1] how pools can be used with notifications to make multiple subgroups of listeners recive copies of the notification.

When all listeners use a pool, there are no listeners consuming the notification queue that notifiers publish messages too. This queue will continue to grow, as can bee seen below queue listing:

rabbitmqctl list_queues name messages consumers auto_delete

Listing queues ...
pool-listener 0 1 false 293 0 false

The atteched file contains a small reproducer. - Sends notifications - A notification listener that does not use a pool - A notification listener using a pool

When running and only the queue have no consumers and continues to grow.

Some mechanism should clear the messages of the queue when all listeners are using one of more pools.


Revision history for this message
Harald Jensås (harald-jensas) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

Fix proposed to branch: master

Changed in oslo.messaging:
assignee: nobody → Ken Giusti (kgiusti)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to oslo.messaging (master)

Submitter: Zuul
Branch: master

commit 855a85fa2daca96ab7d13d5db7684f241a7c18b3
Author: Kenneth Giusti <email address hidden>
Date: Mon Mar 11 09:31:38 2019 -0400

    Clarify the documentation for pooled Notification Listeners

    Change-Id: I184b045edaa8e61f075df576992426e94bf7386a
    Closes-Bug: #1814544

Changed in oslo.messaging:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.messaging 9.6.0

This issue was fixed in the openstack/oslo.messaging 9.6.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers