[SERVER-62181] JStests including multiple parallel migrations with failpoints shouldn't be run in the config server stepdown suites Created: 19/Dec/21 Updated: 29/Oct/23 Resolved: 04/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0, 5.2.0-rc4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Paolo Polato | Assignee: | Paolo Polato |
| 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 | ||||||||||||||||
| Backport Requested: |
v5.2
|
||||||||||||||||
| Sprint: | Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 156 | ||||||||||||||||
| Description |
|
A JS test defining a sequence of commands like
May reach a deadlock state when a step-down event occurs after having issued the shard command for moveChunk1, but before sending out the one for moveChunk2, provoked by the fact that:
The behaviour described in 1) and 2) matches the designed functionality of the BalancerCommandsScheduler (and the legacy MigrationManager). The proposal is then to solve the problem by avoiding the execution of the affected tests in stepdown suites. |
| Comments |
| Comment by Githook User [ 04/Jan/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: (cherry picked from commit 68b1c9ad4fe1c4015c587968bc23b7ec45c5dd17) |
| Comment by Githook User [ 21/Dec/21 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |