[SERVER-32568] The `migration_sets_fromMigrate_flag.js` test is not compatible with sharding continuous stepdown suite Created: 05/Jan/18 Updated: 30/Oct/23 Resolved: 09/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | 3.4.19, 3.6.3, 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| 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: |
v3.6, v3.4
|
||||||||
| Sprint: | Sharding 2018-01-15 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The `migration_sets_fromMigrate_flag.js` test occasionally fails in the continuous stepdown suite because the config server balancer steps down and cases moveChunk to run one time too many, which causes more 'i' entries to be present in the recipient's oplog. Specifically, from the logs it can be seen that the migration, which fails due to 'failMigrationLeaveOrphans' happening twice due to the balancer recovery:
This test should be blacklisted from the continuous stepdown suite. |
| Comments |
| Comment by Githook User [ 16/Nov/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: (cherry picked from commit a9d076d8642c13859588c3bc111b3c9af08cea2f) |
| Comment by Githook User [ 13/Jan/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message:
(cherry picked from commit a9d076d8642c13859588c3bc111b3c9af08cea2f) |
| Comment by Githook User [ 09/Jan/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message:
|