From 8582646036acd63fbb822fa3d945f725d55b3007 Mon Sep 17 00:00:00 2001 From: Sasha Date: Tue, 25 Jun 2024 01:55:44 +0200 Subject: [PATCH] add node health from status-go#4628 --- informational/req-res-reliability.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/informational/req-res-reliability.md b/informational/req-res-reliability.md index d1e5b94..789418e 100644 --- a/informational/req-res-reliability.md +++ b/informational/req-res-reliability.md @@ -16,6 +16,17 @@ Descriptions of mentioned protocols do not define some of the real world use cas ## 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 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.