[SERVER-60008] Disable the distributed lock ping thread in lagged_config_secondary.js Created: 16/Sep/21 Updated: 29/Oct/23 Resolved: 17/Sep/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 5.1.0 |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Allison Easton | Assignee: | Allison Easton |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2021-09-20 | ||||
| Participants: | |||||
| Linked BF Score: | 28 | ||||
| Description |
|
If the distributed lock pinger runs after stopping replication and before the insert into the config database, the optime will be bumped and the insert will hang waiting for the higher optime to be replicated. This has happened on slower variants causing the test to timeout. We should disable the dist lock manager similar to what is done in readConcern_atClusterTime_noop_write.js |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 17/Sep/21 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |