[SERVER-41096] ContinuousStepdown thread and resmoke runner do not synchronize properly on the "stepdown permitted file" and "stepping down file" Created: 10/May/19 Updated: 29/Oct/23 Resolved: 20/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.11, 4.2.0-rc2, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Max Hirschhorn |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bkp, tig-concurrency | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v4.2, v4.0
|
||||||||||||||||||||||||||||||||||||
| Steps To Reproduce: | I am able to show this race on v4.0 by applying the following patch and running yield_group.js in the concurrency_sharded_with_stepdowns suite. Note that this only repro's on v4.0, since the replication team completed the "avoid closing connections on stepdown" project in 4.1.x.
|
||||||||||||||||||||||||||||||||||||
| Sprint: | STM 2019-07-01 | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 18 | ||||||||||||||||||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||||||||||||||||||
| Description |
|
Before running workload teardowns, the fsm runner's main thread But the continuous stepdown thread does the following:
This allows the following interleaving:
|
| Comments |
| Comment by Githook User [ 21/Jun/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: Changes the file-based protocol for controlling when stepdowns are (cherry picked from commit eea65efbdd4f20022973cf38455c22c5b62af9f3) |
| Comment by Githook User [ 21/Jun/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: Changes the file-based protocol for controlling when stepdowns are (cherry picked from commit eea65efbdd4f20022973cf38455c22c5b62af9f3) |
| Comment by Githook User [ 20/Jun/19 ] |
|
Author: {'name': 'Max Hirschhorn', 'email': 'max.hirschhorn@mongodb.com', 'username': 'visemet'}Message: Changes the file-based protocol for controlling when stepdowns are |
| Comment by Vesselina Ratcheva (Inactive) [ 05/Jun/19 ] |
|
I started seeing this very frequently in |