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

[bug]: sometimes rpc work queue gets exhausted #41

Closed
chrisguida opened this issue Jan 28, 2022 · 5 comments
Closed

[bug]: sometimes rpc work queue gets exhausted #41

chrisguida opened this issue Jan 28, 2022 · 5 comments
Assignees
Labels
P2 - Desirable high prioity, nice-to-haves
Milestone

Comments

@chrisguida
Copy link
Contributor

This causes all downstream services to freak out

# docker exec -it bitcoind.embassy bitcoin-cli getblockchaininfo
error: couldn't parse reply from server

WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

@chrisguida chrisguida added the P1 - Blocks Release This issue must be addressed before the coming release is shipped label Jan 28, 2022
@chrisguida chrisguida added this to the EOS v0.3.0 milestone Jan 28, 2022
@chrisguida chrisguida self-assigned this Jan 28, 2022
@ProofOfKeags
Copy link
Contributor

Are we misusing it? Is this problem a symptom of a low workqueue or us abusing the rpc?

@chrisguida
Copy link
Contributor Author

chrisguida commented Jan 28, 2022

I think it's issues with system instability, combined with using the rpc much more heavily

I will try doubling the default workqueue to see if the issues subside

@ProofOfKeags
Copy link
Contributor

possibly addressed by a solution to Start9Labs/community-services#9

@chrisguida
Copy link
Contributor Author

chrisguida commented Feb 14, 2022

P2ing this in favor of Start9Labs/community-services#9

Also changing -getinfo (~60s) call to getrpcinfo (~1s) in rpc health check should help a lot: 6ec5f3a

@chrisguida chrisguida added P2 - Desirable high prioity, nice-to-haves and removed P1 - Blocks Release This issue must be addressed before the coming release is shipped labels Feb 14, 2022
@MattDHill MattDHill moved this to Todo in Service Issues Apr 20, 2022
@kn0wmad
Copy link
Contributor

kn0wmad commented Jun 10, 2022

Closing in favor of #63, which in turn should be closed by #72

@kn0wmad kn0wmad closed this as completed Jun 10, 2022
Repository owner moved this from Todo to Done in Service Issues Jun 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 - Desirable high prioity, nice-to-haves
Projects
Status: Done
Development

No branches or pull requests

3 participants