Add TTL to AMQP messages
Bug #1053614 reported by
Russell Bryant
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oslo-incubator |
Fix Released
|
Medium
|
Brent Eagles | ||
| Grizzly |
Fix Released
|
Medium
|
Brent Eagles | ||
Bug Description
Both RabbitMQ and Qpid support adding a TTL to messages. The TTL allows us to set an amount of time a message can sit in a queue before expiring and getting deleted. The particular case where I think this would be useful is any time that we do an rpc.call(). In that case, we already have a timeout defined for how long we wait for a response before we give up and move on. If the message for a call() has not been pulled from a queue when we hit the timeout, ideally it *never* gets processed. A TTL would accomplish that. There is still the possibility that we time out in the middle of a message being processed, but this would still be an improvement.
| affects: | openstack-common → oslo |
| tags: | added: rpc-api-review |
| Changed in oslo: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in oslo: | |
| assignee: | nobody → Brent Eagles (beagles) |
| Changed in oslo: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to oslo-incubator (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to oslo-incubator (master) | #2 |
| Changed in oslo: | |
| status: | In Progress → Fix Committed |
| Changed in oslo: | |
| milestone: | none → grizzly-3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/