flaky test test_pageserver_gc_compaction_idempotent[after_restart] #10517
Assignees
Labels
t/bug
Issue Type: Bug
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Feb 4, 2025
## Problem Hopefully this can resolve #10517. The reason why the test is flaky is that after restart the compute node might write some data so that the pageserver flush some layers, and in the end, causing L0 compaction to run, and we cannot get the test scenario as we want. ## Summary of changes Ensure all L0 layers are compacted before starting the test. Signed-off-by: Alex Chi Z <chi@neon.tech>
winter-loo
pushed a commit
to winter-loo/neon
that referenced
this issue
Feb 4, 2025
## Problem Hopefully this can resolve neondatabase#10517. The reason why the test is flaky is that after restart the compute node might write some data so that the pageserver flush some layers, and in the end, causing L0 compaction to run, and we cannot get the test scenario as we want. ## Summary of changes Ensure all L0 layers are compacted before starting the test. Signed-off-by: Alex Chi Z <chi@neon.tech>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://neonprod.grafana.net/d/fddp4rvg7k2dcf/regression-test-failures?orgId=1&var-test_name=test_pageserver_gc_compaction_idempotent%5Bafter_restart%5D&from=now-7d&to=now&timezone=utc&var-restrict=true&var-max_count=100&var-reference=$__all&var-ignore_reference=refs%2Fpull%2F0000%2Fmerge
The test case tries to create a scenario that restarting the pageserver causes gc-compaction produces image layers of the same key range but in a different generation. However, it seems hard to make it stable to produce such case. I'm looking into ways to fix it.
The text was updated successfully, but these errors were encountered: