[SERVER-44997] blacklist create_index_background_unique* workloads from concurrency suites with transactions and stepdowns/primary kills Created: 06/Dec/19 Updated: 29/Oct/23 Resolved: 03/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Daniel Ernst |
| 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: | Execution Team 2020-01-13, Execution Team 2019-12-30 | ||||
| Participants: | |||||
| Linked BF Score: | 18 | ||||
| Description |
|
The createIndexes command is not resilient to errors like HostUnreachable and InterruptedDueToReplStateChange. Presently, the create_index_background_unique.js and create_index_background_unique_capped.js workloads fail frequently in suites like concurrency_sharded_multi_stmt_txn_kill_primary because these suites prompt these sorts of errors and rely on lower-level retry logic to handle them. These workloads should be blacklisted from concurrency_sharded_multi_stmt_txn_kill_primary, concurrency_sharded_multi_stmt_txn_terminate_primary, and concurrency_sharded_multi_stmt_txn_with_stepdowns. |
| Comments |
| Comment by Githook User [ 03/Jan/20 ] |
|
Author: {'name': 'Daniel Ernst', 'email': 'daniel.ernst@mongodb.com'}Message: |