Fix socket reset errors when counting#82
Merged
Conversation
Contributor
Author
Owner
|
Thank you so much for your contribution! I really appreciate that you not only found the bug but also fixed it. Great work! I’ll try to release the new version as soon as possible. |
This file contains hidden or 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
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.

When trying to count the number of documents in several collections at once, an error is thrown for all the collections:
But it's actually none of those possible causes - perhaps this is only some DOS protection of mongodb.com and is not present on self-hosted databases, either way, the count requests being sent sequentially eliminates this issue 👍