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

Got two "Block Size is too Big" errors running v0.19.10 #2632

Closed
lukestokes opened this issue Jul 13, 2018 · 5 comments
Closed

Got two "Block Size is too Big" errors running v0.19.10 #2632

lukestokes opened this issue Jul 13, 2018 · 5 comments

Comments

@lukestokes
Copy link

You can see the relevant logs here:

https://gist.github.com/lukestokes/7421398c19efacb0f31ee6315f3fff83

{"next_block_num":24111132,"block_size":65537,"max":65536}
{"next_block_num":24117399,"block_size":65540,"max":65536}

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.

@lukestokes
Copy link
Author

@lukestokes
Copy link
Author

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

@mvandeberg
Copy link
Contributor

Are you running master since the fix was merged?

@lukestokes
Copy link
Author

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
Building from master = 0.19.10

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.

@mvandeberg
Copy link
Contributor

mvandeberg commented Jul 19, 2018

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 and it still happens then there is something else going on.

Master is considered stable enough for production. However, because 0.19.5 and 0.19.10 are both supported releases, we are having stable point to the 0.19.5 release track and master point to the 0.19.10 release track. When 0.20.0 is released there will only be one supported release and stable will point to 0.20.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants