[SERVER-42714] Log replication recovery oplog application completion at level 0 Created: 08/Aug/19 Updated: 29/Oct/23 Resolved: 12/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.13, 4.2.1, 4.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||
| Participants: | |||||||||
| Description |
|
We currently log the completion of replication recovery oplog application at level 2. The number of these log messages does not scale linearly with the number of ops applied during recovery, so it should be fine to log it at level 0, and it would make it easier to determine when replication recovery has finished in production scenarios where log verbosity levels may be at the default. |
| Comments |
| Comment by Githook User [ 04/Sep/19 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: (cherry picked from commit bb877832ca374ec380fd64c1570f16038dfc5b8f) |
| Comment by Githook User [ 04/Sep/19 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: (cherry picked from commit bb877832ca374ec380fd64c1570f16038dfc5b8f) |
| Comment by Githook User [ 12/Aug/19 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |
| Comment by William Schultz (Inactive) [ 12/Aug/19 ] |
|
Code review url: https://mongodbcr.appspot.com/498680014/ |