[SERVER-63077] Fix migration_coordinator_killop_in_critical_section.js test Created: 28/Jan/22 Updated: 29/Oct/23 Resolved: 31/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tommaso Tocci | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding EMEA 2022-02-07 |
| Participants: |
| Description |
|
The test is wrongly using the "hangInRefreshFilteringMetadataUntilSuccessInterruptible" to hang the migration, in fact this fail point is used twice in the migration code and it will cause the migration to block earlier then the test is expecting. So the test hang for 10 min and it work by accident just because the periodicConsistencyChecker is triggering a migration recovery after 10 min. |
| Comments |
| Comment by Githook User [ 28/Jan/22 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |