ROX-21319: Increase DB connection retries #1349
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
dcaravel
changed the title
|
Images are ready for the commit at 7cf102b. To use the images, use the tag |
|
@dcaravel: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
RTann
approved these changes
Dec 12, 2023
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.
Increase the number of DB connection retries before exiting to be a total of 5 minutes (up from 3 minutes).
--
CI jobs will report failure if a scanner pod restarts, and scanner will exit/restart after 3 minutes currently
18 retries * 10 seconds = 180 seconds = 3 minutesA previous CI failure showed the database available 1 minutes after scanner had exited.
Increasing retries should reduce the frequency of CI failures due to pod restarts.
30 retries * 10 seconds = 300 seconds = 5 minutes