[SERVER-33771] Vectored inserts should not generate optimes for multi-statement transactions Created: 08/Mar/18 Updated: 27/Oct/23 Resolved: 23/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Louis Williams |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage NYC 2018-03-26 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently, performing vectored inserts generates OpTimes for every insert operation, which sets the commit_timestamp on the current WiredTiger transaction for every operation here. This is problematic because calling prepare_transaction is not possible after a commit timestamp has been set. The OpTime should be generated once the transaction commits. |
| Comments |
| Comment by Louis Williams [ 23/Mar/18 ] |
|
This was fixed by |
| Comment by Louis Williams [ 15/Mar/18 ] |
|
I don't believe this actually a problem, and I think I was mistaken when I filed this initially.
geert.bosch Let me know if you think this logic is correct. I also can confirm this because the prepare function would fail if a timestamp were set before it was called, and this is not the case. |