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.
Full details of the missed blocks:
https://gist.github.com/lukestokes/71491e0b369ec14358c30c17b321dd80
https://gist.github.com/lukestokes/ed0f60055e882ba90255334148c275d8
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 master since the fix was merged?
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.
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.
Most helpful comment
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
masterand it still happens then there is something else going on.Master is considered stable enough for production. However, because
0.19.5and0.19.10are both supported releases, we are havingstablepoint to the0.19.5release track andmasterpoint to the0.19.10release track. When0.20.0is released there will only be one supported release andstablewill point to0.20.0.