Add RabbitMQ healthcheck to prevent startup race conditions #3568
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: guptapratykshh <[email protected]>
shlokgilda
added
the
redundant
Contributor
Author
|
it is mentioned in the description |
Contributor
|
superseded by #3613 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Added health check to rabbitmq to make sure it is fully initialized before other services connect. rabbitmq can take up to 60 secs to finish syncing its mnesia table on first startup, which was causing some ci timeouts. this fix allows rabbitmq enough time to start up correctly and stops premature connection attempts.
Logs - https://github.com/chaoss/augur/actions/runs/20908242825/job/60065967943?pr=3534
looking at the logs more carefully gives aspect that actual failure is augur-1 tried to connect to database and then postgreSQL was still initializing the error - "ERROR: connecting to database". after that augur-1 exited with 254 , postgreSQL became ready at and rabbitmq was just still booting normally.
This PR fixes #3548
Signed commits