-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kvserver: simplify closed ts management for splits #57405
Copy link
Copy link
Closed
Labels
A-kv-closed-timestampsRelating to closed timestampsRelating to closed timestampsA-multiregionRelated to multi-regionRelated to multi-regionC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Description
Currently, we forward closed timestamps coming from the Provider to maxClosed.Forward(r.mu.initialMaxClosed). Once we get log-driver closed timestamps, we can get rid of tracking this initialMaxClosed, and instead we should have the SplitTrigger copy the LHS's closed ts to the RHS's RangeStateApplyKey.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-closed-timestampsRelating to closed timestampsRelating to closed timestampsA-multiregionRelated to multi-regionRelated to multi-regionC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)