Set higher timeout for Elasticsearch/OpenSearch container startup #26881
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
Frequent I/O Errors we got lately seem to be related to that.
yrodiere
approved these changes
Jul 22, 2022
There was a problem hiding this comment.
Elasticsearch initialization never takes more than 7s on my laptop, and I've never had any problem with <time>20000</time> on the Hibernate Search CI, so that's weird...
I guess the GitHub Actions VMs are (much) slower than those of Hibernate Search's CI for some reason :/
Anyway, if it works, +1 from me.
|
Well, I had a look at one particular failure and it was actually still starting after 20 seconds. So let's try that and see how it goes. |
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.
Frequent I/O Errors we got lately seem to be related to that.