Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test_sharding_split_smoke instability #9802

Open
jcsp opened this issue Nov 19, 2024 · 0 comments
Open

test_sharding_split_smoke instability #9802

jcsp opened this issue Nov 19, 2024 · 0 comments
Assignees
Labels
a/tech_debt Area: related to tech debt a/test Area: related to testing

Comments

@jcsp
Copy link
Collaborator

jcsp commented Nov 19, 2024

Timeouts on pageserver startup while intializing page cache
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9637/11892066435/index.html#/testresult/94da16e9e07308f4

Is 16 pageservers too many when multiplied by the page cache size? Is it memory pressure? Should we use fewer pageservers in this test?

@jcsp jcsp added a/test Area: related to testing a/tech_debt Area: related to tech debt labels Nov 19, 2024
github-merge-queue bot pushed a commit that referenced this issue Nov 20, 2024
## Problem

This test uses a gratuitous number of pageservers (16). This works fine
when there are plenty of system resources, but causes issues on test
runners that have limited resources and run many tests concurrently.

Related: #9802

## Summary of changes

- Split from 2 shards to 4, instead of 4 to 8
- Don't give every shard a separate pageserver, let two locations share
each pageserver.

Net result is 4 pageservers instead of 16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/tech_debt Area: related to tech debt a/test Area: related to testing
Projects
None yet
Development

No branches or pull requests

2 participants