[SERVER-51775] Failpoint to disable periodic uptime reporter thread should instead just disable uptime reporting Created: 21/Oct/20 Updated: 29/Oct/23 Resolved: 03/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Jason Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2020-11-16, Sharding 2020-11-30, Sharding 2020-12-14 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The disableShardingUptimeReporterPeriodicThread failpoint stops the whole uptime reporter thread, but this is overkill for the intended purpose of not doing uptime reporter writes on the configsvrs (because this thread is also responsible for refreshing the balancer state and CWRWC defaults). This failpoint should be renamed to disableShardingUptimeReporting, and its effect changed to just skipping/short-circuiting reportStatus(). |
| Comments |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Jason Zhang', 'email': 'jason.zhang@mongodb.com', 'username': 'jz1242'}Message: |