Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
Fully Compatible
-
ALL
-
v4.4, v4.2, v4.0
-
Sharding 2020-04-06, Sharding 2020-04-20
-
7
Description
Dist lock pint and sharding uptime reporter threads need to have an option to stop running for testing purpose. One way is to add fail points.
Attachments
Issue Links
- is related to
-
SERVER-51775 Failpoint to disable periodic uptime reporter thread should instead just disable uptime reporting
-
- Closed
-
- related to
-
SERVER-51683 Await configRS optime replication before to stop it in lagged_config_secondary.js
-
- Closed
-