From 49acfd772cb4cbb92c85d631d33a2b37c3083b1d Mon Sep 17 00:00:00 2001 From: danisharora099 Date: Tue, 23 Jul 2024 19:39:39 +0530 Subject: [PATCH] chore: clarifications for node health when disparity in protocol health --- standards/application/req-res-reliability.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/standards/application/req-res-reliability.md b/standards/application/req-res-reliability.md index 1bc393f..3b3a701 100644 --- a/standards/application/req-res-reliability.md +++ b/standards/application/req-res-reliability.md @@ -40,13 +40,14 @@ Node health is a metric meant to determine the connectivity state of a light nod We consider this reliability to be dependent on amount of simultaneous connections to responsive service nodes. Unfortunately the more connections light node establishes - the more bandwidth is consumed. To address this we RECOMMEND following states: -- unhealthy - no connections to service nodes are available regardless of protocol; +- unhealthy: + - no connections to service nodes are available regardless of protocol. - minimally healthy: - - Filter has one service node connection; - - LightPush protocol has one service node connection; + - Filter has one service node connection AND LightPush protocol has one service node connection. - sufficiently healthy: - - Filter has at least 2 connections available to service nodes; - - LightPush has at least 2 connections available to service nodes; + - Filter has at least 2 connections available to service nodes AND LightPush has at least 2 connections available to service nodes. + +If one of the protocols is unhealthy or minimally healthy, while the other is sufficiently healthy - overall node health SHOULD be considered as unhealthy or minimally healthy respectively. ### Peers and connection management