-
Notifications
You must be signed in to change notification settings - Fork 38
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
Getting odd status code some calls #99
Comments
What do you mean by above sentence? You are running a goloop node that has configured to accept 1000 batch RPC requests? |
@sink772 - Correct, we set this by exec-ing into the container. goloop system config rpcIncludeDebug true
goloop system config rpcBatchLimit 1000 We have been doing some experimenting around what to set the batch from (10, to 100, to 1000) as we are trying to be able to send massive volumes of RPC calls to a node for indexing. We just built this tool - https://github.com/sudoblockio/icon-extractor - which seems to be overloading goloop with requests. I started another issue #100 around performance as this issue is really about the "ProxyIsClosed" error coming from the OnClose method. They could be related though if the node is crashing a lot and this is just the error we get at the end. When we have been doing high load tests, we haven't been typically seeing this error though and don't want assume they are related. |
Can you provide us the goloop node logs when the "ProxyIsClosed" error occurs? We need to get some hints from the logs. |
We are getting some odd responses that we have never seen before on sejong.
Contract exists. Call works fine against solidwallet / geometry endpoints but failing against a bare metal node that has batch set to 1000.
The text was updated successfully, but these errors were encountered: