Skip to content

Add startup probe to RabbitMQ#2050

Merged
Zerpet merged 2 commits intomainfrom
startup-probe
Feb 11, 2026
Merged

Add startup probe to RabbitMQ#2050
Zerpet merged 2 commits intomainfrom
startup-probe

Conversation

@Zerpet
Copy link
Copy Markdown
Member

@Zerpet Zerpet commented Feb 5, 2026

This closes #2016

Note to reviewers: remember to look at the commits in this PR and consider if they can be squashed

Summary Of Changes

  • Add a startup probe to check that cluster is fully formed

Local Testing

Added unit and integration test.

@Zerpet Zerpet added this to the v2.20.0 milestone Feb 5, 2026
Copy link
Copy Markdown
Member

@MirahImage MirahImage left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should attempt to remember to switch to the new API/cli call once the oldest supported RabbitMQ version has it.

Copy link
Copy Markdown
Contributor

@mkuratczyk mkuratczyk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought that the eval approach would be for PoC only, but as long as me move to something better soon, I guess it's fine. Alternatively, we could call the new CLI/API and ignore errors if it doesn't exist so that this feature works only with versions that ship the new CLI/API

@Zerpet
Copy link
Copy Markdown
Member Author

Zerpet commented Feb 11, 2026

Initially it was a PoC, but this interim change is beneficial and solves a long outstanding edge case with cluster formation. I left a TODO comment to replace the probe with an actual HTTP call when rabbit supports it.

@Zerpet Zerpet merged commit 330ad51 into main Feb 11, 2026
76 of 78 checks passed
@Zerpet Zerpet deleted the startup-probe branch February 11, 2026 12:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Leverage cluster size hint for service readiness

3 participants