[SERVER-53440] [v4.4] plan_cache_drop_database.js assertion too strict Created: 18/Dec/20 Updated: 29/Oct/23 Resolved: 18/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| 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 | ||||
| Sprint: | Execution Team 2020-12-28 | ||||
| Participants: | |||||
| Linked BF Score: | 21 | ||||
| Description |
|
The DatabaseDropPending assertion in plan_cache_drop_database.js is too strict. We expect the DatabaseDropPending error to originate from the bulk writer but that's not always the case. We should simply check for the DatabaseDropPending error code and avoid checking if the error originated from the bulk writer. |
| Comments |
| Comment by Githook User [ 18/Dec/20 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |