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

RabbitMQ queues are not declared as replicated #1745

Open
cailyoung opened this issue Aug 2, 2023 · 2 comments
Open

RabbitMQ queues are not declared as replicated #1745

cailyoung opened this issue Aug 2, 2023 · 2 comments

Comments

@cailyoung
Copy link

We noticed during a RabbitMQ node outage recently that log_message_saving was unavailable to the jobs service despite 2/3 of the RabbitMQ nodes being up. After investigation we noticed that (all?) of the queues declared by this and other services are 'Classic' queues, which exist only on whichever node the client that declared them was connected to at declaration time.

It should be considered to allow replicated queues, either via quorum queues or streams, so that multi-node RabbitMQ systems can be operated safely and not cause consumer failures for ReportPortal.
@DzmitryHumianiuk
Copy link
Member

@cailyoung definitely makes sense

@DzmitryHumianiuk
Copy link
Member

related:
#1744
reportportal/service-jobs#86
#1745

This was referenced Aug 7, 2023
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cailyoung @DzmitryHumianiuk