Alex Chi Z. 700885471f fix(test): only test num of L1 layers in compaction smoke test (#9186) ...

close https://github.com/neondatabase/neon/issues/9160

For whatever reason, pg17's WAL pattern seems different from others,
which triggers some flaky behavior within the compaction smoke test.

## Summary of changes

* Run L0 compaction before proceeding with the read benchmark.
* So that we can ensure the num of L0 layers is 0 and test the
compaction behavior only with L1 layers.

We have a threshold for triggering L0 compaction. In some cases, the
test case did not produce enough L0 layers to do a L0 compaction,
therefore leaving the layer map with 3+ L0 layers above the L1 layers.
This increases the average read depth for the timeline.

---------

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

2024-10-02 17:42:35 +01: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

storcon: provide an az id in metadata.json from neon local (#8897)

2024-09-03 15:11:30 +01:00

common_types.py

python: allow using allowed_errors.py (#7719)

2024-05-13 15:16:23 +03:00

http.py

fix(test): only test num of L1 layers in compaction smoke test (#9186)

2024-10-02 17:42:35 +01:00

many_tenants.py

Rename some S3 usages to "remote storage" in exposed messages (#8999)

2024-09-17 19:15:01 +02:00

remote_storage.py

python: allow using allowed_errors.py (#7719)

2024-05-13 15:16:23 +03:00

utils.py

test: copy dict to avoid error on retry (#8811)

2024-08-23 14:43:08 +01:00