status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

update networking, update hardware requirements, set up health.md (#3020)

This commit is contained in:
sacha 2021-10-21 16:18:46 +02:00 committed by GitHub
parent c3c8e27011
commit dc3c23788a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 20 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/the_nimbus_book/src/hardware.md
View File

@ -13,7 +13,7 @@
Note that in order to process incoming validator deposits from the eth1 chain, you will need to run an eth1 client in parallel to your eth2 client. While it is possible to use a third-party service like [Infura](/infura-guide.md), if you choose to run your own eth1 client locally, you'll need more memory and storage.
For example, you'll need at least another **290GB SSD** to run [geth fast sync](/eth1.md) on mainnet.
For example, you'll need at least another **500GB SSD** to run [geth fast sync](/eth1.md) on mainnet.
To future proof your setup we recommend a **1TB SSD**.

11
docs/the_nimbus_book/src/health.md
View File

@ -32,3 +32,14 @@ To run it:
*TBC -See [here](https://github.com/jclapis/rp-pi-guide/blob/main/Native.md#monitoring-your-pis-performance) for more*
## Keep an eye on the logs
## Keep an eye on the metrics
## Grafana
## Relevant REST API queries
## External tools
### beaconchain

13
docs/the_nimbus_book/src/networking.md
View File

@ -11,12 +11,15 @@ A collection of tips and tricks to help improve your network connectivity.
## Monitor your Peer count
If your Peer count is low (less than `15`) and/or you repeatedly see the following warning:
```
WRN 2021-05-08 12:59:26.669+00:00 Peer count low, no new peers discovered topics="networking" tid=1914 file=eth2_network.nim:963 discovered_nodes=9 new_peers=0 current_peers=1 wanted_peers=160
```
If your Peer count is low (less than `15`) and/or you repeatedly see either of the following warnings:
It means that Nimbus was unable to find a sufficient number of peers to guarantee stable operation, and you may miss attestations and blocks as a result.
`Peer count low, no new peers discovered...`
or
`No peers for topic, skipping publish...`
It means that Nimbus is unable to find a sufficient number of peers to guarantee stable operation, and you may miss attestations and blocks as a result.
Most commonly, this happens when your computer is not reachable from the outside and therefore won't be able to accept any incoming peer connections.