Actions
Bug #61639
openamqp: notifications are not retired on persistent topic
% Done:
0%
Source:
Community (user)
Tags:
notifications, amqp backport_processed
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Description
if the broker goes down, notifications are not sent when the broker recovers
Updated by Yuval Lifshitz 11 months ago
was not able to reproduce the issue, following these steps: https://gist.github.com/yuvalif/e58e264bafe847bc5196f95be0e704a2
however, race conditions similar to the ones found in kafka may happen in amqp as well
Updated by Yuval Lifshitz 11 months ago
- Status changed from New to Fix Under Review
- Pull request ID set to 52110
Updated by Casey Bodley 11 months ago
- Status changed from Fix Under Review to Pending Backport
- Backport set to pacific quincy reef
Updated by Backport Bot 11 months ago
- Copied to Backport #61918: pacific: amqp: notifications are not retired on persistent topic added
Updated by Backport Bot 11 months ago
- Copied to Backport #61919: reef: amqp: notifications are not retired on persistent topic added
Updated by Backport Bot 11 months ago
- Copied to Backport #61920: quincy: amqp: notifications are not retired on persistent topic added
Updated by Backport Bot 11 months ago
- Tags changed from notifications, amqp to notifications, amqp backport_processed
Updated by Casey Bodley 10 months ago
- Related to Bug #62264: [ FAILED ] TestAMQP.IdleConnection (30132 ms) added
Updated by Casey Bodley 7 months ago
@Yuval this is a high-priority bug fix that hasn't been backported to quincy or pacific
Actions