Alex Chi Z. 92d95b08cf fix(pageserver): extend split job key range to the end (#10484) ...

## Problem

Not really a bug fix, but hopefully can reproduce
https://github.com/neondatabase/neon/issues/10482 more.

If the layer map does not contain layers that end at exactly the end
range of the compaction job, the current split algorithm will produce
the last job that ends at the maximum layer key. This patch extends it
all the way to the compaction job end key.

For example, the user requests a compaction of 0000...FFFF. However, we
only have a layer 0000..3000 in the layer map, and the split job will
have a range of 0000..3000 instead of 0000..FFFF.

This is not a correctness issue but it would be better to fix it so that
we can get consistent job splits.

## Summary of changes

Compaction job split will always cover the full specified key range.

Signed-off-by: Alex Chi Z <chi@neon.tech>

2025-01-23 00:15:46 +00:00

..

benches

pageserver: coalesce index uploads when possible (#10248)

2025-01-14 21:10:17 +00:00

client

fix(page_service pipelining): tenant cannot shut down because gate kept open while flushing responses (#10386)

2025-01-16 20:34:02 +00:00

compaction

chore: fix clippy lints 2024-12-06 (#10138)

2024-12-16 15:33:21 +00:00

ctl

pageserver: add page_trace API for debugging (#10293)

2025-01-15 19:07:22 +00:00

pagebench

pageserver: issue concurrent IO on the read path (#9353)

2025-01-22 15:30:23 +00:00

src

fix(pageserver): extend split job key range to the end (#10484)

2025-01-23 00:15:46 +00:00

test_data

pageserver: add layer visibility calculation (#8511)

2024-08-01 09:25:35 +00:00

Cargo.toml

fix(page_service pipelining): tenant cannot shut down because gate kept open while flushing responses (#10386)

2025-01-16 20:34:02 +00:00