[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: |
| 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). |