[SERVER-45767] Blacklist create_database.js from concurrency_replication_multi_stmt_txn Created: 24/Jan/20 Updated: 29/Oct/23 Resolved: 27/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Maria van Keulen |
| 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-27 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 29 | ||||||||||||
| Description |
|
concurrency_replication_multi_stmt_txn will retry transactions that fail with retriable errors, including NoSuchTransaction. Any workload, such as create_database.js, that expects errors that cannot be blindly retried upon, can time out inside concurrency_replication_multi_stmt_txn due to the following sequence: suite starts transaction with FSM state -> test encounters and ignores non retriable error -> transaction implicitly aborts due to non retriable error -> suite attempts to commit the transaction -> commit fails with NoSuchTransaction -> suite retries the transaction -> suite starts transaction with FSM state The transaction will keep retrying indefinitely, failing every time, since the non retriable error keeps occurring and getting ignored. Since this is an incompatibility between create_database.js and the suite, it should be blacklisted from this suite. |
| Comments |
| Comment by Githook User [ 27/Jan/20 ] |
|
Author: {'username': 'mvankeulen94', 'name': 'Maria van Keulen', 'email': 'maria.vankeulen@mongodb.com'}Message: This test is incompatible with this set of suites. |