Update replica-configuration.txt #978
Closed
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
|
merged! |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Apr 18, 2022
* (DOCS-15246): 4.2.20 changelog * add changelog include
mongo-cr-bot
pushed a commit
that referenced
this pull request
Apr 18, 2022
* (DOCS-15246): 4.2.20 changelog * add changelog include
mongo-cr-bot
pushed a commit
that referenced
this pull request
Apr 18, 2022
* (DOCS-15246): 4.2.20 changelog * add changelog include
mongo-cr-bot
pushed a commit
that referenced
this pull request
Apr 18, 2022
* (DOCS-15246): 4.2.20 changelog * add changelog include
jeff-allen-mongo
added a commit
that referenced
this pull request
Apr 18, 2022
* (DOCS-15246): 4.2.20 changelog * add changelog include
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 22, 2025
(cherry picked from commit a9aa853) Co-authored-by: lindseymoore <[email protected]>
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 28, 2025
* RUBY-1369 Collection change stream integration test * RUBY-1369 try_next implementation * RUBY-1369 Move to spec/integration * RUBY-1369 Got try_next working when there are changes * RUBY-1369 Test try_next with no changes * RUBY-1369 Document try_next * RUBY-1369 Change change stream resume logic more to retry once only * RUBY-1369 Apply current resume behavior to try_next * RUBY-1369 Add docstrings for change_stream_resumable? * RUBY-1369 Document how to restart change streams and when they are resumed by the driver automatically * RUBY-1369 failCommand is 4.0+ only * RUBY-1369 These are now non-resumed * RUBY-1369 Repair the logic yet again. The concept of "retrying once" is apparently much more difficult than it first appears * RUBY-1369 Repair this test again and try another way to not have it be stuck in a getmore loop * RUBY-1369 Use timeout-interrupt to stop tests hanging forever on change stream reads * RUBY-1369 Force a successful getMore prior to failing them. I believe change stream drops documents upon a reset without startAtOperationTime, hence right now we can't reliably test initial getMores failing * RUBY-1369 Need to clear fail points only on tests using them if I want to run others on servers < 4.0
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.
No description provided.