Loading...

XML

Word

Printable

JSON

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.2.7, 4.4.0-rc3, 4.7.0, 4.0.22
Affects Version/s: None
Component/s: Sharding
Labels:
- sharding-4.4-stabilization
- sharding-wfbf-day

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.4, v4.2, v4.0
Sprint:
Sharding 2020-04-06, Sharding 2020-04-20
Linked BF Score:
7
Confidence Status:
None
Work Order:
3

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name:
None
Goal Link:
None

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.

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

Assignee:: Haley Connelly
Reporter:: Misha Tyulenev (Inactive)
Participants:: Githook User, Haley Connelly, Misha Tyulenev
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: Aug 05 2019 04:14:42 PM UTC
Updated:: Oct 29 2023 10:18:22 PM UTC
Resolved:: Apr 06 2020 07:22:02 PM UTC
Confidence Status Last Update:: 31/Mar/20 8:16 PM