[SERVER-21755] Add periodic collection of db.serverStatus({oplog: 1}) to FTDC Created: 03/Dec/15 Updated: 08/Sep/20 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Mark Benvenuto |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | move-sec | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Security 2020-09-21 | ||||||||
| Participants: | |||||||||
| Description |
|
Knowing the earliest and latest optimes would give us the ability to track the approximate time span the oplog represents over time. This would aid in investigating any issues with truncation via oplog stones when random sampling is used on startup. |
| Comments |
| Comment by Mark Benvenuto [ 08/Sep/20 ] |
|
This duplicates |
| Comment by Bruce Lucas (Inactive) [ 29/Nov/18 ] |
|
We did this in |