-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Something is wrong with the ledger shrinking #35110
Comments
As mentioned on Discord, I am highly suspect of this:
Running a node with The only scenario in which I'd expect your node to have so few slots is if you had just spun it up from scratch (no pre-existing ledger). Your node does not appear to be reporting metrics, so I can't do much digging unfortunately. If you still have your logs, grepping for below might give us something to go off of:
|
You could check
Anyway, bellow 2 logs (
|
@steviez |
I asked the guys from the Telegram group to do the same grep ~20K before the restart and now. I currently have ~500. But I deleted the ledger. I think they didn't delete it. |
@diman-io - Thanks for the responses, I have enough information / think I sufficiently understand the problem so probably no need to request / post any further reports |
@steviez hi, I was just wondering if there has been any progress with this issue? |
Apologies, I just saw your comment in other issue and realized I never responded. After doing some testing on our side, I think we're actually going to deprecate FIFO as an option. The perf gains that it provided over the default are not as great after some optimization we did to the default ( I'm not 100% sure when we'll roll this out, but I would swap over when you get a chance |
Problem
I received this on all three machines (one voting, two backup).
The validator continued to operate for ~2 hours after the cluster stopped until the attempt to create a snapshot.
The text was updated successfully, but these errors were encountered: