[SERVER-78365] Investigate removing ignore_prepare=force Created: 22/Jun/23 Updated: 06/Feb/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Gregory Noma |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Sprint: | Execution NAMR Team 2023-07-24, Execution NAMR Team 2023-08-07, Execution Team 2023-11-13, Execution Team 2023-11-27, Execution Team 2024-03-18 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
This option significantly complicates reasoning about behaviors around prepared transactions, so removing it should be high on our list of behaviors to remove. |
| Comments |
| Comment by Louis Williams [ 20/Nov/23 ] |
|
I don't see a path forward to eliminate this API as long as we want a safety mechanism from WiredTiger to prevent us from introducing data corruption bugs. |
| Comment by Louis Williams [ 01/Nov/23 ] |
|
There's quite a bit to discuss here. But first I'll just provide background. Data corruption bugs like As of today, we have a few users of this override:
This override is required unconditionally on secondaries due to the problems described in If we don't like the current API, it seems like we need to rethink the API a bit to deliver something that works better for our current code. We still want to respect these requirements:
|