-
Notifications
You must be signed in to change notification settings - Fork 4.1k
kv: Add server option for maximum number of intents per WriteIntentError for scans #64783
Copy link
Copy link
Closed
Labels
A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.A-storageRelating to our storage engine (Pebble) on-disk storage.Relating to our storage engine (Pebble) on-disk storage.C-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)N-followupNeeds followup.Needs followup.O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.T-kvKV TeamKV Team
Description
We added batching of discovered intents for subsequent resolutions during sst exports similar to what scan does (Issue: #59704, PR: #64131). On top of that, the change provides an option to limit number of collected intents to keep batch size predictable.
We may consider using the same approach to MVCCScan to make number of collected intents capped.
Epic: CRDB-2554
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-kv-transactionsRelating to MVCC and the transactional model.Relating to MVCC and the transactional model.A-storageRelating to our storage engine (Pebble) on-disk storage.Relating to our storage engine (Pebble) on-disk storage.C-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)N-followupNeeds followup.Needs followup.O-postmortemOriginated from a Postmortem action item.Originated from a Postmortem action item.T-kvKV TeamKV Team