[SERVER-9487] Question about oplog Created: 27/Apr/13  Updated: 10/Dec/14  Resolved: 29/Apr/13

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

Type: Question Priority: Major - P3
Reporter: zijian_he Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Replication Set


Participants:

 Description   

I ran the following command:
SECONDARY> db.printReplicationInfo();
configured oplog size: 24650.5005859375MB
log length start to end: 14410435secs (4002.9hrs)
oplog first event time: Sun Nov 11 2012 17:32:23 GMT+0800 (CST)
oplog last event time: Sat Apr 27 2013 12:26:18 GMT+0800 (CST)
now: Sat Apr 27 2013 12:26:19 GMT+0800 (CST)
I found that the oplog has not been sync for a very long time.
I would like to how to resync again and the reason why the oplog has not been sync for such a long time.



 Comments   
Comment by Scott Hernandez (Inactive) [ 27/Apr/13 ]

These kind of questions are best asked on the google groups forum here (http://groups.google.com/group/mongodb-user); jira is meant for filing feature requests and bugs related to the server.

I am confused by your question. Can you try to ask again with more information about what you believe is wrong? Also, what do you mean by resync and what would you expect it to fix/help?

The output from your commands show that the oplog on that secondary started in November 2012 and is up to date as of 12:26 AM CST ( the last oplog entry matches the time when the command was run).

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