waku-org
/
specs
mirror of https://github.com/waku-org/specs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add node health from status-go#4628

This commit is contained in:
Sasha 2024-06-25 01:55:44 +02:00
parent 7371dabdca
commit 8582646036
No known key found for this signature in database
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
informational/req-res-reliability.md
View File

@ -16,6 +16,17 @@ Descriptions of mentioned protocols do not define some of the real world use cas
## Suggestions ## Suggestions
### Node health
As a useful metric to define and implement for determining quality of provided service by a node:
- unhealthy - no peer connections are available regardless of protocol;
- minimally healthy:
- Relay has less than 4 peers connected;
- Filter and LightPush has one per each peer connection available;
- sufficiently healthy:
- Relay has minimum 4 peers connected;
- more than 1 connection in Filter and at least 2 connections available in LightPush;
### Peer and connection management ### Peer and connection management
Each protocols should retain a pool of reliable peers. In case a protocol failed to use any peer more than once - connection to it should be dropped and new peer should be added to the pool instead. Each protocols should retain a pool of reliable peers. In case a protocol failed to use any peer more than once - connection to it should be dropped and new peer should be added to the pool instead.