nacking a rabbit message is not enough to have another consumer get it
Bug #1320205 reported by
Vincent Ladeuil
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Triaged
|
Medium
|
Unassigned |
Bug Description
Discovered when fixing bug #1320000 , nacking a message put it back on the queue but since we use prefetch_count=1 in baisc_qos() the message stays in the local queue and doesn't "go back" to the server.
We need to either:
- stop using prefetch_count=1 (rabbit's doc says it's good for performance reasons),
- change out implementation to also close the queue/channel/
- something else
Changed in uci-engine: | |
milestone: | uce-0 → backlog |
To post a comment you must log in.
Experimenting with amqp for the debci, pitti had a test showing that killing the worker put the not-yet-acked message back to the queue.