[SERVER-62758] migration_recovers_unfinished_migrations.js should not run on sharding_continuous_config_stepdown suites Created: 19/Jan/22 Updated: 29/Oct/23 Resolved: 21/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | Sharding EMEA 2022-01-24 | ||||
| Participants: | |||||
| Linked BF Score: | 153 | ||||
| Description |
|
As a result of a CSRS steps down then steps up, the logic of migration_recovers_unfinished_migrations.js test is affected causing the execution to hang indefinitely. Indeed, the CSRS retries to run pending chunk migrations (this is part of the balancer logic). The test was not designed to support this case, and that is also irrelevant to its purpose. The solution is to exclude this test from being performed when the CSRS steps down. |
| Comments |
| Comment by Githook User [ 21/Jan/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |