Skip to content

storage: snapshots ingested into L0 during decommission #80589

@lunevalex

Description

@lunevalex

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

Metadata

Metadata

Assignees

Labels

C-investigationFurther steps needed to qualify. C-label will change.T-storageStorage Team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions