Logical error in blockless fanout of zmq

Bug #1300539 reported by Li Ma
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.messaging
Fix Released
Low
Li Ma

Bug Description

In impl_zmq.py: _multi_send()

# This supports brokerless fanout (addresses > 1)
for queue in queues:
    (_topic, ip_addr) = queue
    _addr = "tcp://%s:%s" % (ip_addr, conf.rpc_zmq_port)
    if method.__name__ == '_cast':
        eventlet.spawn_n(method, _addr, context,
                         _topic, msg, timeout, envelope,
                         _msg_id)
        return
    return method(_addr, context, _topic, msg, timeout,
                  envelope)

The blockless fanout doesn't take effect and it only processes
the FIRST one by returning after the first loop.

Li Ma (nick-ma-z)
Changed in oslo.messaging:
assignee: nobody → Li Ma (nick-ma-z)
Li Ma (nick-ma-z)
Changed in oslo.messaging:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to oslo.messaging (master)

Fix proposed to branch: master
Review: https://review.openstack.org/84310

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

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

commit de2de36a4a1a69cbbfedec9a8d0619a50e49f77b
Author: Li Ma <email address hidden>
Date: Mon Mar 31 19:00:41 2014 -0700

    Logical error in blockless fanout of zmq

    The blockless fanout doesn't take effect and it
    only processes the FIRST one by returning after the first loop.

    Change-Id: Iad071ab455e36be7b26637b286ca9f83fea4a019
    Closes-Bug: #1300539

Changed in oslo.messaging:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in oslo.messaging:
milestone: none → juno-1
status: Fix Committed → Fix Released
Mark McLoughlin (markmc)
Changed in oslo.messaging:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.