-
Notifications
You must be signed in to change notification settings - Fork 795
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
Got two "Block Size is too Big" errors running v0.19.10 #2632
Comments
Full details of the missed blocks: https://gist.github.com/lukestokes/71491e0b369ec14358c30c17b321dd80 |
Happened again, which makes me wonder if this is something specific to 0.19.10 since it didn't used to happen: https://gist.github.com/lukestokes/4a06e9b1d078be89dea0a0498bab56ee |
Are you running |
No, I'm still running v0.19.10. Just seems odd to me that this has happened three times since running the 0.19.10 release if not's directly related to 0.19.10 in some way. Building from stable = 0.19.5 Is that correct? If master is consider "stable" (this is getting a little confusing) enough to run in production, I can rebuild and keep running to see if it keeps happening if that would be helpful. For now, I'm back on 0.19.5. I'm curious to see if it happens there also and we just haven't seen it before because we didn't have as many full blocks. |
It is related to block size. At the very least the bug we discovered that easily explains what happened is related to block size. If you run Master is considered stable enough for production. However, because |
You can see the relevant logs here:
https://gist.github.com/lukestokes/7421398c19efacb0f31ee6315f3fff83
My hunch is v0.19.10 is doing something strange to bring in more transactions than it should and is blowing up when it tries to produce the block.
I may switch back to my v0.19.5 producing server if this continues.
The text was updated successfully, but these errors were encountered: