[SERVER-50368] oplog drops to zero unexpectedly Created: 18/Aug/20  Updated: 19/Aug/20  Resolved: 18/Aug/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 4.2.3
Fix Version/s: None

Type: Question Priority: Minor - P4
Reporter: Barry Johnson Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Minor Change
Participants:

 Description   

On a single Secondary node of a replica set, after resizing a 1+ TB oplog a total of three (3) times (-> 51200 MB -> 25600 MB -> 5120 MB), the oplog dropped to zero/empty, and the mongod log shows no indication of having restarted.

Please help us understand why the oplog unexpectedly became empty.



 Comments   
Comment by Barry Johnson [ 18/Aug/20 ]

Submitted incorrectly, by mistake. Please ignore.

Generated at Thu Feb 08 05:22:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.