Remove health checks against opensearch #1620
Merged
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
mbertrand
approved these changes
Sep 30, 2024
Member
mbertrand
left a comment
mbertrand
left a comment
There was a problem hiding this comment.
👍 , though when I initially started it up I got lots of connection refused messages because all the daily ETL tasks started running and opensearch wasn't ready yet for the indexing requests.
mbertrand
added
Waiting on author
and removed
Needs Review
mbertrand
pushed a commit
that referenced
this pull request
Oct 4, 2024
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.
What are the relevant tickets?
N/A
Description (What does it do?)
This remove the healthchecks because I've been hitting an exception locally that causes OpenSearch to be considered unhealthy which then causes docker compose to shutdown the app. There's an upstream bug in OpenSearch that's been open for 3 week but no known workaround.
How can this be tested?
You should still be able to run
docker compose upand nothing changes