[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: |
|
||||||||
| 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:
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) } aclimasensordb:PRIMARY> db.oplog.rs.find({}, {ts:1}).sort({$natural:1}).limit(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 |