Auto-tools/Projects/Pulse/PulseGuardian: Difference between revisions

Line 29: Line 29:
= Notes =
= Notes =


As we RabbitMQ's management plugin API doesn't give us the user who created a queue, we'll probably have to poll RabbitMQ to detect queues that aren't assigned to any user and assign each of them to the user of the consumer currently consuming them (reminder: In our pattern, we should only have one consumer maximum per queue).  If we have not found an owner of a queue by the time it hits DEL_QUEUE_SIZE (because the consumer never stays connected long enough), the queue will be deleted.
As we RabbitMQ's management plugin API doesn't give us the user who created a queue, we'll have to poll RabbitMQ to detect queues that aren't assigned to any user and assign each of them to the user of the consumer currently consuming them (reminder: in our pattern, we should only have one consumer maximum per queue).  If we have not found an owner of a queue by the time it hits DEL_QUEUE_SIZE (because the consumer never stays connected long enough), the queue will be deleted with no warning (or, optionally, just a warning to the admin(s)).


= Implementation =
= Implementation =
Confirmed users
1,927

edits