[SERVER-46188] Blacklist write_conflicts_with_non_txns.js from sharded transaction passthrough suites due to maxTimeMS incompatibility Created: 14/Feb/20 Updated: 29/Oct/23 Resolved: 18/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | William Schultz (Inactive) |
| 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 | ||||||||||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||||||
| Description |
|
The write_conflicts_with_non_txns.js tries to run that an insert times out via maxTimeMS, but currently maxTimeMS is not propagated from a mongoS to a shard which makes this check unreliable. We should blacklist this test from sharded passthrough suites until maxTimeMS works as expected in this scenario. We have lots of transactions test coverage in sharded clusters so I don't think blacklisting temporarily is a problem. |
| Comments |
| Comment by Githook User [ 21/Feb/20 ] |
|
Author: {'username': 'will62794', 'name': 'William Schultz', 'email': 'william.schultz@mongodb.com'}Message: (cherry picked from commit 3e8fea7b03c7cb7fbed5e68714b0f3cfd663016c) |
| Comment by Githook User [ 18/Feb/20 ] |
|
Author: {'name': 'William Schultz', 'username': 'will62794', 'email': 'william.schultz@mongodb.com'}Message: |