Skip to content

kvserver: simplify closed ts management for splits #57405

@andreimatei

Description

@andreimatei

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.

Metadata

Metadata

Assignees

Labels

A-kv-closed-timestampsRelating to closed timestampsA-multiregionRelated to multi-regionC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions