-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvserver: investigate SingleDelete for raft log truncation #8979
Copy link
Copy link
Open
Labels
A-kv-replicationRelating to Raft, consensus, and coordination.Relating to Raft, consensus, and coordination.C-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.T-kvKV TeamKV Teamo-perf-efficiencyRelated to performance efficiencyRelated to performance efficiency
Description
@tbg on 2023-04-10:
Re-using this issue to focus exclusively on SingleDelete for the raft log, see #8979 (comment).
On #4321, @Simkha mentioned SingleDelete and its handling in compactions:
The following link points to a comment in CompactionIterator::NextFromInput(), the comment explains when presence of SingleDelete would compact out (i.e. clear) the stored key and the SingleDelete record. This iterator is used during meltable flush.
If you can adapt your code to meet the restrictions of SingleDelete, then I think, it could be useful.
Jira issue: CRDB-6156
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-replicationRelating to Raft, consensus, and coordination.Relating to Raft, consensus, and coordination.C-performancePerf of queries or internals. Solution not expected to change functional behavior.Perf of queries or internals. Solution not expected to change functional behavior.T-kvKV TeamKV Teamo-perf-efficiencyRelated to performance efficiencyRelated to performance efficiency