[SERVER-43099] Reenable random chunk migration failpoint for concurrency with_balancer suites Created: 30/Aug/19 Updated: 29/Nov/23 Resolved: 07/Feb/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Alexander Taskov (Inactive) | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding 2019-12-16, Sharding 2019-12-30, Sharding 2020-01-13, Sharding EMEA 2021-11-29, Sharding EMEA 2021-12-13, Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10, Sharding EMEA 2022-05-30, Sharding EMEA 2022-09-05, Sharding EMEA 2022-09-19, Sharding EMEA 2022-10-03, Sharding EMEA 2022-10-17, Sharding EMEA 2022-10-31, Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12, Sharding EMEA 2022-12-26, Sharding EMEA 2023-01-09, Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 113 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
The random migration failpoints have possible exposed various failures and will be disabled until we investigate the BFs that were encountered. Once we have resolved these issues, the failpoint should be reenabled. |
| Comments |
| Comment by Githook User [ 07/Feb/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |
| Comment by Silvia Surroca [ 01/Jun/22 ] |
|
Given that no pre-splitting is happening anymore and the balancer is now taking into consideration data size, the only possible "random" migration that can happen is moving back and forward one chunk for tests working with few or no data. Also, random move chunk workloads are anyway testing the same use case. For now, linking the ticket to PM-2652 because the "random chunk migration" test behaviour should be rethink after the future new balancer implementation. |
| Comment by Jordi Serra Torrens [ 13/Jan/22 ] |
|
In addition to the failures mentioned above, there's still one test failure pending to be understood:
Understood ^: The test leaves idle cursors opens. This makes the stopBalancer/checkOrphans checks at the end of the fixture hang, because the rangeDeleter cannot progress due to the open cursors. |
| Comment by Blake Oler [ 17/Oct/19 ] |
|
Note that when we re-enable the random balancer policy, we may have to create a way for workloads to opt out of the randomness, such as the workload in |