-
Notifications
You must be signed in to change notification settings - Fork 302
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
pd: remove client sync timeouts #2932
Conversation
Spinning up a node to test this prior to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggesting a higher timeout, if you don't have objections. The process I used to test was:
- create fullnode with https rpc access
- cherry-pick these commits on top of v0.58.1
- bounce pd
- run
pcli -n <node> view sync
three times
2s wasn't enough, 10s was enough, seems like a happy medium for now. I think we're both eager to wash our hands of the timeout tedium. If you +1 this change, I'm happy to get it out the door.
pd: re-enable req-resp timeout pd(oblivious): increase timeout to 2s pd: fix type inferrence error
ca11ed1
to
00040bc
Compare
I've rebased the changes here into a single commit for the timeout-removal, so it's more straightforward to cherry-pick into a patch release branch. Prior to merge, I'll test again on a dedicated node, and confirm pcli sync behavior is sound. |
Was able to sync pcli three times to latest block height. |
Part of #2918 (cc @conorsch ). We have isolated that the stream terminates because of the timeout on polling compact blocks. This PR reenable the req-resp timeout and increase the polling timeout to
2s
.