[SERVER-61620] Set multiple log levels for the messages generated by the BalancerCommandsScheduler Created: 19/Nov/21 Updated: 29/Oct/23 Resolved: 22/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | Backlog |
| Fix Version/s: | 5.2.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2021-11-29 |
| Participants: |
| Description |
|
The current version of BalancerCommandsScheduler defines a big set of log messages, all of them enabled by default. Now that the component is stable, non-critical messages should be generated only when the DEBUG level is active to avoid flooding the log file. |
| Comments |
| Comment by Githook User [ 22/Nov/21 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |