Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[MU] Disconnection: the distributed way #5334

Open
chibenwa opened this issue Nov 20, 2024 · 0 comments
Open

[MU] Disconnection: the distributed way #5334

chibenwa opened this issue Nov 20, 2024 · 0 comments
Labels
customer security

Comments

@chibenwa
Copy link
Member

chibenwa commented Nov 20, 2024 •
edited
Loading

In a brand new server/data/data-rabbitmq implement a version of the DisconnectorNotifier leveraging a broadcast thus enabing to call disconnect endpoint only on a single node of the cluster.

Follow broadcast best practicces

  • Create one exchange fanout
  • Create one (quorum) queue per node based on a UUID
  • Use QUEUE-TTL
  • Monitor in a healthcheck the consumer and recreate it if missing.
  • Handle RabbitMQ reconnection

Cc @guimard
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
customer security
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chibenwa