[SERVER-39685] Have oplog_visibility.js be robust to a tailable cursor prematurely being exhausted Created: 20/Feb/19  Updated: 29/Oct/23  Resolved: 21/Feb/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.9

Type: Bug Priority: Major - P3
Reporter: Daniel Gottlieb (Inactive) Assignee: Daniel Gottlieb (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-02-25
Participants:
Linked BF Score: 43

 Description   

First, limit inserts to avoid rolling over the oplog.

Second, accept the case where hasNext returns false and have the test re-issue the query.



 Comments   
Comment by Githook User [ 21/Feb/19 ]

Author:

{'name': 'Daniel Gottlieb', 'email': 'daniel.gottlieb@mongodb.com', 'username': 'dgottlieb'}

Message: SERVER-39685: Have oplog_visibility.js cope with server behaviors.
Branch: master
https://github.com/mongodb/mongo/commit/1d6995441c39e5761f923dc7f9be01dd354ec3af

Generated at Thu Feb 08 04:52:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.