You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently timeouts were added to the HTTP RPC server in #16859 and some arbitrary timeouts were chosen with a call for feedback.
For local hosts the timeouts are mostly fine, but if you run a node on a server ReadTimeout is much too low, as it's reliant on the client speed rather than the server. This is specifically an issue when trying to send large batched requests to get block or transaction information, which causes unnecessary timeout errors on slower connections.
I would recommend setting ReadTimeout to at least 15-30 seconds, and possibly also increasing WriteTimeout to 30-60 seconds to accommodate the large responses specifically from log requests which can often be in the megabytes. IdleTimeout is fine.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Recently timeouts were added to the HTTP RPC server in #16859 and some arbitrary timeouts were chosen with a call for feedback.
For local hosts the timeouts are mostly fine, but if you run a node on a server ReadTimeout is much too low, as it's reliant on the client speed rather than the server. This is specifically an issue when trying to send large batched requests to get block or transaction information, which causes unnecessary timeout errors on slower connections.
I would recommend setting ReadTimeout to at least 15-30 seconds, and possibly also increasing WriteTimeout to 30-60 seconds to accommodate the large responses specifically from log requests which can often be in the megabytes. IdleTimeout is fine.
The text was updated successfully, but these errors were encountered: