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.
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
Mongodb driver switch to mongo-driver #8140
Mongodb driver switch to mongo-driver #8140
Changes from all commits
127aaa3
d62affa
1682794
6e5f64b
d14105f
7286eb0
3d0cb6b
5d9fe4a
a74f924
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 code seems a little weird to me. The
mongo.Client
type is resilient to failovers, so a failedPing
does not necessarily indicate that the client should be restarted. If the server is in the cluster of failing over during thePing
, theClient
will re-calibrate its view of the cluster and figure out what changed.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.
I assume this happens automatically while we ping the server, correct? If that is the case I think this is just for safety reasons in case something bad happens. I agree that mostly the next connection attempt will fail too but I also think it doesn't hurt to try it again?
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.
Instead of creating a completely new
Client
, maybe we can just try thePing
again? This is the biggest downfall of using thePing
method in general: it's good for testing server connectivity but if the server is undergoing a transient state change, it will report a failure even though it's not really a failure.If you want to avoid risk, though, perhaps it is best to keep the existing behavior and just recreate the
Client
. I'll defer that to you.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.
I personally think that creating a fresh client which adds a minimal overhead compared to reusing the old client is the better choice here.