This repository was archived by the owner on Dec 22, 2020. It is now read-only.
Feature/fix cursor timeout #106
Open
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
This is a weird one; we have a collection with 51 million records that we need to mirror to postgres and we kept hitting the CURSOR_NOT_FOUND exception. As recommended on https://github.com/mongodb/mongo-ruby-driver/wiki/FAQ#i-keep-getting-cursor_not_found-exceptions-whats-happening I tried adding the
:timeout => falseparameter, which did not change anything. However, once I additionally removed the "with_retries" around it everything works. I don't know why that would break it, I'm not much of a ruby guy, but it doesn't seem to be doing anything near as important as getting all entries in a large collection, so unless you have a suggestion for another way to fix this I suggest this fix.