[SERVER-45898] read_write_concern_defaults_application doesn't declare usage of transactions Created: 31/Jan/20 Updated: 29/Oct/23 Resolved: 05/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Kevin Pulo |
| 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: | Sharding 2020-02-10 | ||||
| Participants: | |||||
| Linked BF Score: | 47 | ||||
| Description |
|
For sure needs the uses_transactions tag. Not sure about uses_multi_shard_transaction (suspect |
| Comments |
| Comment by Githook User [ 05/Feb/20 ] |
|
Author: {'name': 'Kevin Pulo', 'username': 'devkev', 'email': 'kevin.pulo@mongodb.com'}Message: |
| Comment by Kevin Pulo [ 02/Feb/20 ] |
|
Given that read_write_concern_defaults_application.js only spins up a single-shard test cluster, I'm thinking uses_multi_shard_transaction shouldn't be necessary. |