Vlad Lazar eadabeddb8 pageserver: use the same job size throughout the import lifetime (#12026) ...

## Problem

Import planning takes a job size limit as its input. Previously, the job
size came from a pageserver config field. This field may change while
imports are in progress. If this happens, plans will no longer be
identical and the import would fail permanently.

## Summary of Changes

Bake the job size into the import progress reported to the storage
controller. For new imports, use the value from the pagesever config,
and, for existing imports, use the value present in the shard progress.

This value is identical for all shards, but we want it to be versioned
since future versions of the planner might split the jobs up
differently. Hence, it ends up in `ShardImportProgress`.

Closes https://github.com/neondatabase/neon/issues/11983

2025-05-28 15:19:41 +00:00

..

src

pageserver: use the same job size throughout the import lifetime (#12026)

2025-05-28 15:19:41 +00:00

Cargo.toml

cover direct IO + concurrent IO in unit, regression & perf tests (#11585)

2025-04-17 15:53:10 +00:00