[QAARQ-16] RabbitMQ: concurrent activations and multi-site support Created: 09/Mar/17  Updated: 17/Dec/18  Resolved: 10/Jul/17

Status: Closed
Project: Queued Asynchronous Activation over RabbitMQ
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jann Forrer Assignee: Unassigned
Resolution: Workaround exists Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

The current RabbitMQ modules use a single queue for all activations. This means that (as opposed to the magnolia standard activation process):

  • no concurrent activations are possible
  • a «single point of failure» is added to the activation process. If the queue ist blocked / corrupted for some reason, activations are blocked on a global level until you fix the problem (which can take time and therefore lead to even more issues, e.g. run-up of messages that lead to RabbitMQ memory problems, etc.).

Adding support for concurrent activations might not be trivial. But for multi-site installations, it should be easy to add multi-queue support (one queue per site). This would make concurrent activations possible on per-site basis and also limit activation problems to particular sites.



 Comments   
Comment by Thomas Comiotto [ 06/Jul/17 ]

Can you please assign this ticket to Jann. Thanks, Thomas

Comment by Richard Gange [ 10/Jul/17 ]

It's possible to achieve this using a fanout exchange and extra consumer threads. See https://www.rabbitmq.com/tutorials/tutorial-three-python.html.

Comment by Richard Gange [ 10/Jul/17 ]

It might be a good idea if we covered the workaround in the docu or a wiki page. I'll look into creating a how-to for it.

Generated at Mon Feb 12 10:38:50 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.