-
Notifications
You must be signed in to change notification settings - Fork 674
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
[Network] long delay between receiving a block validation request and getting a response #5366
Comments
Seems the root cause is that these nodes are just super-backlogged with HTTP requests:
Looks like we have two candidates for network RPC optimization: |
I think it would be good to get more clear on what exactly this ticket aims to solve. It's certainly fine for this ticket to be "we have a problem, we should figure out what we want to do about it", but I think we should figure out what that work is and split that into individual tickets. IMO there are a number of known improvements here: [signer] Track 429 block submission failures in the database and resubmit them following a block validation response - this is a big one It also appears that you've identified two potential big wins:
I'd note that the |
Maybe the signals got mixed in the lines somewhere, but it's not quite this. We only mirror |
Ah, I also found the Slack thread where we discussed this, and there was an issue where the stacking script was trying to re-broadcast a stack-extend every ~20 seconds (we've fixed that issue) |
The foundation nakamoto testnet miner sees this:
The hiro nodes and signers see this:
Why is there such a long delay between the signer submitting a block proposal and the node receiving it?
The text was updated successfully, but these errors were encountered: