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.

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

Roll out AWS managed rabbitmq with replication #283

Closed
matusdrobuliak66 opened this issue Jul 21, 2023 · 11 comments
Closed

Roll out AWS managed rabbitmq with replication #283

matusdrobuliak66 opened this issue Jul 21, 2023 · 11 comments
Assignees
Labels
during maintenance Changes that have to be adressed in maintenance timewindows p:mid-prio t:enhancement New feature or request

Comments

@matusdrobuliak66
Copy link
Contributor

No description provided.

@mrnicegyu11
Copy link
Member

Tracked by ITISFoundation/osparc-issues#1018

@mrnicegyu11
Copy link
Member

This seems blocked by simcore not being able to handle the amqps protocoll (currently only amqp). Please follow up @sanderegg

@mrnicegyu11
Copy link
Member

mrnicegyu11 commented Aug 7, 2023

Blocked until ITISFoundation/osparc-simcore#4567 propagates to staging/prod (it is in Sundae3)

@mrnicegyu11
Copy link
Member

We use it now in the ZMT deployment. It is in.

@mrnicegyu11 mrnicegyu11 changed the title Investigate AWS managed rabbitmq Roll out AWS managed rabbitmq with replication Nov 27, 2023
@mrnicegyu11 mrnicegyu11 reopened this Nov 27, 2023
@YuryHrytsuk
Copy link
Collaborator

Amazom MQ Cluster deployment for high availability:

@YuryHrytsuk
Copy link
Collaborator

YuryHrytsuk commented Dec 6, 2023

Amazon broker config reference:

Terraform aws_mq_broker doc:

Deployment mode reference:

@YuryHrytsuk
Copy link
Collaborator

⚠️ The mq.t3.micro instance type does not support cluster deployment.

@YuryHrytsuk
Copy link
Collaborator

YuryHrytsuk commented Dec 6, 2023

@YuryHrytsuk
Copy link
Collaborator

A good short article explaining mandatory maintenance of Amazon MQ. It leads to many conclusions like: single instance broker will leave us without rabbit during maintenance.

@YuryHrytsuk
Copy link
Collaborator

@YuryHrytsuk
Copy link
Collaborator

All the code is merged. It can be closed after next staging and next prod release.

@YuryHrytsuk YuryHrytsuk added during maintenance Changes that have to be adressed in maintenance timewindows and removed blocked / paused labels Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
during maintenance Changes that have to be adressed in maintenance timewindows p:mid-prio t:enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants