-
Notifications
You must be signed in to change notification settings - Fork 501
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
Investigate reaping sql timeouts in horizon #5320
Labels
Comments
This was referenced May 16, 2024
stellar-core, stellar-horizon, and postgres share the same host, which is 8c16GB , and a ssd with a maximum of 5000 iops.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version are you using?
Horizon: 2.30.0
Go: 1.22
What did you do?
What did you expect to see?
If history-retention is set, reaping should succeed without any issues:
What did you see instead?
We have notice reports of reaping failing due to sql timeout errors:
The text was updated successfully, but these errors were encountered: