[SERVER-37625] Collect diagnostic information for replication oplog window Created: 15/Oct/18 Updated: 29/Oct/23 Resolved: 15/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.6 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Emilio Scalise | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SWDI, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||
| Sprint: | Security 2018-11-19 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||||||
| Description |
|
It would be useful to have in the `diagnostic.data` information the information shown with the command db.printreplicationinfo() and in particular the "oplog first event time" over the time. This will allow us to know the replication oplog window metric over the time to troubleshoot replication issues. |
| Comments |
| Comment by Githook User [ 13/Dec/18 ] |
|
Author: {'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto'}Message: Revert " This reverts commit dd17c8ad0fa2b9b71df5f0b00ec77f58b55c4a5b. |
| Comment by Bruce Lucas (Inactive) [ 29/Nov/18 ] |
|
This had an unfortunate unforeseen side effect: see |
| Comment by Githook User [ 15/Nov/18 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |
| Comment by Githook User [ 15/Nov/18 ] |
|
Author: {'name': 'Mark Benvenuto', 'email': 'mark.benvenuto@mongodb.com', 'username': 'markbenvenuto'}Message: |
| Comment by Bruce Lucas (Inactive) [ 15/Oct/18 ] |
|
I think it might be better to add {oplog: true} to the ftdc serverStatus command as this will add oplog earliestTime and latestTime to ftdc. |