[SERVER-54751] Create disallow jstest for reshard and drop collection commands Created: 24/Feb/21 Updated: 29/Oct/23 Resolved: 31/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-234-M3, PM-234-T-lifecycle | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
A new test must be written without using the resharding fixture to make sure that the drop can't happen while resharding is in progress. The reason of this is that the resharding fixture have some metadata checks performed after releasing the resharding failpoint, and, if a concurrent drop (waiting for the distlock) is running, then it will drop everything after the failpoint is released but before the checks, making the test to fail because the collection is not found. |
| Comments |
| Comment by Githook User [ 31/Mar/21 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |