[SERVER-2728] optime of secondary in rs.status() doesn't include no-ops Created: 10/Mar/11  Updated: 06/Dec/22  Resolved: 16/Nov/16

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

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Backlog - Storage Execution Team
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Operating System: ALL
Participants:

 Description   

Makes secondary look far behind the primary



 Comments   
Comment by Eric Milkie [ 07/Mar/14 ]

There may be other ways of solving this without filling the oplog with no-ops.

Comment by Eric Milkie [ 25/Feb/13 ]

I don't think we are using no-ops in replica set oplogs.

Generated at Thu Feb 08 03:01:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.