[SERVER-60719] Hybrid index build side table uses mixed mode writes Created: 14/Oct/21 Updated: 27/Oct/23 Resolved: 19/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Execution Team 2021-12-13, Execution Team 2021-12-27 | ||||||||
| Participants: | |||||||||
| Description |
|
Inserts into the side-table are written as part of the larger transaction doing the logical operation (i.e: insert/update/delete) – inheriting its timestamp. But the drain phase deletes from the side table without a timestamp. This results in a mixed-mode violation. |
| Comments |
| Comment by Connie Chen [ 19/Apr/22 ] |
|
Since mixed-modes is supported by WT, we are closing this as "works as designed" |
| Comment by Connie Chen [ 08/Mar/22 ] |
|
thanks daniel.gottlieb, we'll leave this ticket within the project to be tackled then. |
| Comment by Daniel Gottlieb (Inactive) [ 04/Mar/22 ] |
|
I don't think I was involved in the decision to make this a 6.0 required ticket! But I don't think it's a blocker no. Having talked with keith.bostic on which timestamping patterns are problematic, there wasn't much concern for mixed-mode writes from WT's perspective. From ours mixed mode can be useful and often safe when it's the last write we will be doing to a WT document (typically deleting it). This ticket falls into that benign scenario. |
| Comment by Connie Chen [ 04/Mar/22 ] |
|
daniel.gottlieb - Is this actually a blocker for 6.0? |