[SERVER-62022] Reduce dbCheck info logging in production, log start and stop Created: 13/Dec/21 Updated: 29/Oct/23 Resolved: 18/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.0.6, 4.4.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Josef Ahmad |
| 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: |
v5.0, v4.4
|
||||||||||||
| Sprint: | Execution Team 2021-12-27 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
On release builds, log an info-level entry every N batches. On debug builds, log all entries. These entries consume space in the health log. Additionally, log info-level entries in the health log (always, not just in testing) that indicate when a dbCheck operation starts and stops. |
| Comments |
| Comment by Githook User [ 22/Dec/21 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: (cherry picked from commit f328a35d74b1b98497d3b57db631d51e2c6b4e29) |
| Comment by Githook User [ 21/Dec/21 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: (cherry picked from commit f328a35d74b1b98497d3b57db631d51e2c6b4e29) |
| Comment by Githook User [ 18/Dec/21 ] |
|
Author: {'name': 'Josef Ahmad', 'email': 'josef.ahmad@mongodb.com', 'username': 'josefahmad'}Message: |