openstack team mailing list archive

Thread
Date

openstack team
Mailing list archive
Message #22623

Re: RPC call timeouts

To: Lowery, Mathew <mlowery@xxxxxxxx>
From: Eric Windisch <eric@xxxxxxxxxxxxxxxx>
Date: Fri, 12 Apr 2013 12:08:47 -0400
Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
In-reply-to: <D5C018CAC77E514BA572D79E860DF31C28648FB8@DEN-EXDDA-S12.corp.ebay.com>

> 
> Finally, it appears that when an RPC call times out, the original message, at least is some cases like 'network.hostname' queue, is left in place to be consumed when a consumer is available. This seems like an odd design--if I take corrective action in response to an RPC timeout, I don't think I want that message processed ever. 
> 


For what it is worth, Grizzly introduces TTLs for individual messages as they're injected into RabbitMQ and Qpid.  This was already the behavior for ZeroMQ, in Folsom.

Regards,
Eric Windisch

References

RPC call timeouts
From: Lowery, Mathew, 2013-04-12