Setup healthcheck timeout env variables #675
Merged
Conversation
This file contains 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
|
@freezy-sk this is awesome! Just tested this out and it worked great. This not only helps others who still aren't booted after 10 seconds, but also those who prime quickly are able to exit out of the unnecessary sleep 😁 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For those struggling with setup stuck on Waiting for connection to Elasticsearch... or Waiting for connection to RabbitMQ..., I've added environment variables for healthcheck timeouts.
I've managed to get setup running with
ES_HEALTHCHECK_TIMEOUT=300andRABBITMQ_HEALTHCHECK_TIMEOUT=100This pull request also brings RabbitMQ healthcheck through curl instead of just waiting few seconds