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
Served eth_getLogs err="context canceled" #20426
Comments
This seems to be a nice issue. We'll need to take a closer look into this. |
Thanks @karalabe. Let me know if I can help with anything |
Maybe this PR can help with it? #16070 |
Hi, We are also facing a similar issue. Works (Block 10870000)
Not Working (Block 10800000) -
|
@karalabe We're seeing a similar issue when we make log queries that span more than ~400k blocks (we default to
Edit: The context canceled was coming from a timeout on the client side. It also required increasing the write timeout in geth to keep it from silently timing out on geth's end. This isn't an issue for us, though. |
I am also facing Are there any starting points where one could tune what timeouts and such settings in geth could be tuned for this? |
I did an example on web3.py how to throttle down requests on HTTP timeout reply. Not ideal, but works for now. Ultimately would be nice to be able to have more control over how much data can be requested at once. |
Geth silently closed connections on timeout which caused confusion. With #25457 merged, geth will return a timeout error. You can extend the WriteTimeout if you want your node to run longer queries. Closing. |
System information
Geth version: 1.9.8-stable-d62e9b28
OS & Version: Linux
Expected behaviour
Be able to get the logs from
0x266BFdb2124A68beB6769dC887BD655f78778923
smartcontract since block0x7A2CCB
related to the filter0x526d4ccf8c3d7b6f0b6d4cc0de526d515c87d1ea3bd264ace0b5c2e70d1b2208
.This are the results that I get with Parity v2.5.10-stable:
Actual behaviour
I tried in several machines with the same geth version fully synchronised and I get this response:
Steps to reproduce the behaviour
Backtrace
The text was updated successfully, but these errors were encountered: