-
Notifications
You must be signed in to change notification settings - Fork 4.1k
storage: snapshots ingested into L0 during decommission #80589
Copy link
Copy link
Closed
Labels
C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.T-storageStorage TeamStorage Team
Description
In a recent customer issue we observed that during a decomission, when we were streaming snapshots to a new node 90% of snapshots were ingested into L0. The expectation is that Pebble should be capable to ingest all incoming snapshots into a lower level. The goal of this ticket is perform an investigation to understand why does Pebble behave this way and come up with a proposal for improving the snapshot ingestion path.
Jira issue: CRDB-15336
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-investigationFurther steps needed to qualify. C-label will change.Further steps needed to qualify. C-label will change.T-storageStorage TeamStorage Team