Vlad Lazar 1efaa16260 test: add test for checkpoint timeout flushing (#6950) ...

## Problem
https://github.com/neondatabase/neon/pull/6661 changed the layer
flushing logic and led to OOMs in staging.
The issue turned out to be holding on to in-memory layers for too long.
After OOMing we'd need to replay potentially
a lot of WAL.

## Summary of changes
Test that open layers get flushed after the `checkpoint_timeout` config
and do not require WAL reingest upon restart.
The workload creates a number of timelines and writes some data to each,
but not enough to trigger flushes via the `checkpoint_distance` config.

I ran this test against https://github.com/neondatabase/neon/pull/6661
and it was indeed failing.

2024-03-01 14:43:33 +00:00

..

__init__.py

tests: make neon_fixtures a bit thinner by splitting out some pageserver related helpers (#3977)

2023-04-07 13:47:28 +03:00

allowed_errors.py

pageserver: roll open layer in timeline writer (#6661)

2024-02-19 12:34:27 +00:00

http.py

feat: support lazy, queued tenant attaches (#6907)

2024-02-29 13:26:29 +02:00

many_tenants.py

pagebench-based GetPage@LSN performance test (#6214)

2024-01-24 12:51:53 +01:00

remote_storage.py

pagebench-based GetPage@LSN performance test (#6214)

2024-01-24 12:51:53 +01:00

types.py

pagebench-based GetPage@LSN performance test (#6214)

2024-01-24 12:51:53 +01:00

utils.py

test: add test for checkpoint timeout flushing (#6950)

2024-03-01 14:43:33 +00:00