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.
fix: reduce excessive logging when database is unreachable #17363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: reduce excessive logging when database is unreachable #17363
Changes from 3 commits
3f95841
0448a74
0136b70
8d94c3c
f92e852
4b0fd6a
68867da
6f60cbc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comment is wrong, we don't continually retry because
DialAgent
only waits until we hit a dial error. Once the first error is returned the test is complete and we tear down the context.Furthermore, I don't think the SDK
DialAgent
is really the thing that you care about testing here. It doesn't handle the retries anyways,tailnet
does. Maybe simplify this and just use theWebsocketDialer
and ensure it returns an error.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self-review:
acquireAndRunOne
already logs its own warning - specifically theprovisionerd was unable to acquire job
one is logged when the db is unreachable - soDebug
is what felt most appropriate to me.