Skip to content
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

[6.1.2] Backport - Improve process connection error handling and logging (#6471) #6440

Merged

Conversation

Joerger
Copy link
Contributor

@Joerger Joerger commented Apr 13, 2021

Backports #6471

@Joerger Joerger requested a review from awly April 13, 2021 20:02
@Joerger Joerger changed the title Change direct connect failure log to debug level and omit error message. Tone down direct connect failure log. Apr 13, 2021
@Joerger Joerger changed the title Tone down direct connect failure log. [6.1] Tone down direct connect failure log. Apr 13, 2021
@Joerger Joerger changed the title [6.1] Tone down direct connect failure log. [6.1.2] Tone down direct connect failure log. Apr 13, 2021
@knisbet
Copy link
Contributor

knisbet commented Apr 13, 2021

Not totally sure if it's the case here, but I wanted to share some experience with troubleshooting in gravity. If this works like there is a connection attempt made, that in most configurations fail, and then it falls back into another mechanism in which most configurations will succeed, it makes it difficult to troubleshoot if the first mechanism is expected to work in a particular configuration.

I don't know what the best advice is, but I would probably try to stash the error and bubble up both if that's applicable here. Just wanted to share, since it came up a few times where troubleshooting gravity with fallback logic that might be similar.

lib/service/connect.go Outdated Show resolved Hide resolved
@Joerger Joerger force-pushed the joerger/backport-6.1/fix/direct-connect-failure-log branch from b706867 to 108e4a2 Compare April 15, 2021 18:31
@Joerger Joerger changed the title [6.1.2] Tone down direct connect failure log. [6.1.2] Backport - Improve process connection error handling and logging (#6471) Apr 15, 2021
Copy link
Contributor

@russjones russjones left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bot.

@Joerger Joerger enabled auto-merge (squash) April 20, 2021 23:44
@Joerger Joerger merged commit 00b3267 into branch/v6.1 Apr 21, 2021
@Joerger Joerger deleted the joerger/backport-6.1/fix/direct-connect-failure-log branch April 21, 2021 00:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants