From c23dfe95f5987a07fec74e807dad506ead9a9ae1 Mon Sep 17 00:00:00 2001 From: Sasha Date: Tue, 2 Jul 2024 11:17:17 +0200 Subject: [PATCH] update node health section --- informational/req-res-reliability.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/informational/req-res-reliability.md b/informational/req-res-reliability.md index efef584..8e19425 100644 --- a/informational/req-res-reliability.md +++ b/informational/req-res-reliability.md @@ -28,12 +28,14 @@ Such use cases can be: recovery from offline state, decrease rate of missed mess ### 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; +Metric meant to determine how reliable light node is: +- unhealthy - no connections to service nodes are available regardless of protocol; - minimally healthy: - - Filter and LightPush clients has one per each peer connection available; + - Filter has one service node connection; + - LightPush protocol has one service node connection; - sufficiently healthy: - - more than 1 connection in Filter and at least 2 connections available in LightPush; + - Filter has at least 2 connections available to service nodes; + - LightPush has at least 2 connections available to service nodes; ### Peers and connection management