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
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Which network are you connected to?: custom with aura consensus
I'm trying to send a huge amount (~10K) of requests (personal_sendTransaction) at once to Parity json-rpc endpoint and it crashes with the following message:
2018-03-15 12:05:39 Incoming streams error, closing sever: Error { repr: Os { code: 23, message: "Too many open files in system" } }
2018-03-15 12:05:40 Couldn't open disk map for writing: Too many open files in system (os error 23)
2018-03-15 12:05:41 Couldn't open disk map for writing: Too many open files in system (os error 23)
I will try to use a persistent connection to handle this issue, as it was described in the tickets above.
But I believe that this is a bug with Parity's module too. If I send too many http requests for ex. to Apache or Nginx, they stay alive with accordingly decreased response time. So why does Parity json-rpc module just crash?
@chebykin If you want to handle more connections you need to increase your system's ulimit, I believe it would be the same for Nginx and Apache (depending on mpm)
I'm trying to send a huge amount (~10K) of requests (personal_sendTransaction) at once to Parity
json-rpc
endpoint and it crashes with the following message:I will try to use a persistent connection to handle this issue, as it was described in the tickets above.
But I believe that this is a bug with Parity's module too. If I send too many http requests for ex. to Apache or Nginx, they stay alive with accordingly decreased response time. So why does Parity
json-rpc
module just crash?Relate issues are #6575 and #6516
The text was updated successfully, but these errors were encountered: