[SERVER-47444] Assertion to guard against individual commands inside transactions specifying their own readConcern happens after waiting for readConcern Created: 09/Apr/20 Updated: 29/Oct/23 Resolved: 15/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc2, 4.7.0 |
| Type: | Bug | 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 | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||
| Sprint: | Execution Team 2020-04-20 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 44 | ||||||||||||||||||||
| Description |
|
We have a uassert that should prevent individual transaction statements from specifying their own readConcern. However, we wait for read concern before calling runCommandImpl, which is where our uassert executes. As a result, if we specify a readConcern for a statement following the first statement in the transaction, we will fail the uassert, but not until after actually waiting for the read concern. |
| Comments |
| Comment by Githook User [ 16/Apr/20 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: This fixes a bug where transaction statements specifying their own (cherry picked from commit d1094411f42197b450c466edcdfa2972947df53f) |
| Comment by Githook User [ 15/Apr/20 ] |
|
Author: {'name': 'Maria van Keulen', 'email': 'maria@mongodb.com', 'username': 'mvankeulen94'}Message: This fixes a bug where transaction statements specifying their own |