[SERVER-53236] Disable merge_with_move_primary.js from running on the sharding_csrs_continuous_config_stepdown suite Created: 04/Dec/20 Updated: 29/Oct/23 Resolved: 10/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.4.4, 4.2.13 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-csrs-stepdown-upkeep, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.4, v4.2
|
||||||||
| Sprint: | Sharding 2020-12-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
This test executes several movePrimary commands. The problem appears when the CS primary node steps down during the execution of one of them: the movePrimary may continue its execution on the shards and once the new CS primary node is elected we may end up having two move primary commands being executed at the same time over the same database (the distributed lock is released once the CS primary node is elected). |
| Comments |
| Comment by Githook User [ 18/Jan/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |
| Comment by Githook User [ 18/Jan/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |
| Comment by Githook User [ 10/Dec/20 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |