[SERVER-9348] printReplicationInfo doesn't agree with actual oplog timestamps Created: 13/Apr/13  Updated: 10/Dec/14  Resolved: 13/Apr/13

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

Type: Bug Priority: Major - P3
Reporter: Stan Hu Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-9085 db.replSetInfo() issue with convertin... Closed
Operating System: ALL
Participants:

 Description   

I dropped the oplog.rs collection and re-created it with a 100GB file.

After 8 hours, I printReplicationInfo shows the wrong data:

aclimasensordb:PRIMARY> db.printReplicationInfo()
configured oplog size:   102400MB
log length start to end: 28.997999999905005secs (0.01hrs)
oplog first event time:  Fri Jan 16 1970 14:24:05 GMT-0500 (EST)
oplog last event time:   Fri Jan 16 1970 14:24:34 GMT-0500 (EST)
now:                     Sat Apr 13 2013 13:30:50 GMT-0400 (EDT)

If I actually query the table, I see that the oplogs are properly there:

aclimasensordb:PRIMARY> db.oplog.rs.find({},

{ts:1}

).sort({$natural:-1}).limit(1)
{ "ts" :

{ "t" : 1365874292, "i" : 59 }

}

aclimasensordb:PRIMARY> db.oplog.rs.find({},

{ts:1}

).sort({$natural:1}).limit(1)
{ "ts" :

{ "t" : 1365845252, "i" : 1 }

}

t = 1365845252 is 4/13/2013 2:27:32 AM

t = 1365874292 is 4/13/2013 10:31:32 AM



 Comments   
Comment by Daniel Pasette (Inactive) [ 13/Apr/13 ]

This issue duplicates SERVER-9085

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