[SERVER-41790] Report progress during oplog sampling at startup with higher granularity Created: 17/Jun/19 Updated: 29/Oct/23 Resolved: 20/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Marco Bonezzi | Assignee: | Daniel Ernst |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2019-10-07, Execution Team 2019-12-16, Execution Team 2019-12-30 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In certain situations (.i.e after restoring an EBS snapshot + large oplog), oplog sampling can take longer than expected and there won't be much on the mongod log to understand this. It would be great if the progress rate could be presented on the log to facilitate the diagnostic of such situations. |
| Comments |
| Comment by Githook User [ 20/Dec/19 ] |
|
Author: {'name': 'Daniel Ernst', 'email': 'daniel.ernst@mongodb.com'}Message: |
| Comment by Bruce Lucas (Inactive) [ 12/Dec/19 ] |
|
Once per minute seems a little too infrequent - a user could get concerned if it's not up within a minute and look in the log file to see what's up. 10 seconds seems good. Anything more frequent would not be useful as it would take at least 10 seconds just to go look at the log file to see why it's not starting. |