[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:
Related
related to SERVER-42632 Disable pinger threads that reach out... Closed
related to SERVER-51683 Await configRS optime replication bef... Closed
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: SERVER-51775 Failpoint to disable periodic uptime reporter thread should instead just disable uptime reporting
Branch: master
https://github.com/mongodb/mongo/commit/94864589ce3f349b35ed3ca1597767c0747ab72a

Generated at Thu Feb 08 05:26:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.