-
Notifications
You must be signed in to change notification settings - Fork 463
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
Attempt to perform query just after pageserver restart fails #5620
Comments
This may be a side effect of #5198 in development environments, where Maybe the |
Hmm, I thought it would had supported this still, but agreed, #5198 is to blame.
It's always difficult to remember for me how to configure it, so yes. |
By the way, when pageserver (re)started rather slowly, I observe a failure of the test test_threshold_based_eviction:
Or with a standalone script:
I get:
|
These two invocations are not equivalent anymore because the test configures remote storage but the standalone version does not (yet).
With the python test failures, showing the full stacktrace is useful. Sadly with plain The error here points to our http client we use in tests, which is not useful. Full stacktrace would contain the test and line in test.
The "tenant is not yet ready" is a known issue. There is an open PR for waiting tenants to be ready in the startup by default to get rid of all this flakyness (#4864). |
@koivunej , thanks for the information! |
I promised to understand this before tomorrow's release, and I did: neon/pageserver/src/tenant/timeline/init.rs Line 156 in 7d17f17
So it is as John assumed. |
#5760 will indirectly fix this by always setting up remote storage. Leaving this open while |
Remote storage is required now (see #7722), so closing this. |
Steps to reproduce
Result
Logs, links
.neon/pageserver_1/pageserver.log contains:
===
.neon/endpoints/main/compute.log contains:
The text was updated successfully, but these errors were encountered: