mirrors/tendermint
1
0
Fork 0
mirror of https://github.com/tendermint/tendermint.git synced 2026-01-05 04:55:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: document open file limit in production guide (#4945)

Browse Source 
See e.g. https://github.com/tendermint/tendermint/issues/4925#issuecomment-637929251 for people getting hit by this. Should we document it elsewhere as well?
This commit is contained in:
Erik Grinaker
2020-06-03 11:34:25 +02:00
committed by GitHub
parent 4e6a844d6f
commit 395d58c27c
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/tendermint-core/running-in-production.md
View File

@@ -96,6 +96,11 @@ connection has `MaxPacketMsgPayloadSize`, which is the maximum packet
size and bounded send & receive queues. One can impose restrictions on
send & receive rate per connection (`SendRate`, `RecvRate`).
The number of open P2P connections can become quite large, and hit the operating system's open
file limit (since TCP connections are considered files on UNIX-based systems). Nodes should be
given a sizeable open file limit, e.g. 8192, via `ulimit -n 8192` or other deployment-specific
mechanisms.
### RPC
Endpoints returning multiple entries are limited by default to return 30
@@ -371,6 +376,8 @@ these limits.
[Sysctls to tune the system to be able to open more connections](https://github.com/satori-com/tcpkali/blob/master/doc/tcpkali.man.md#sysctls-to-tune-the-system-to-be-able-to-open-more-connections)
The process file limits must also be increased, e.g. via `ulimit -n 8192`.
...for N connections, such as 50k:
```