logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-01-03 22:53:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: clarifications for node health when disparity in protocol health

Browse Source
This commit is contained in:
danisharora099 2024-07-23 19:39:39 +05:30
parent 6e6be39e2a
commit 49acfd772c
No known key found for this signature in database
GPG Key ID: FBD2BF500037F135
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
standards/application/req-res-reliability.md
View File

@ -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. 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. Unfortunately the more connections light node establishes - the more bandwidth is consumed.
To address this we RECOMMEND following states: 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: - minimally healthy:
- Filter has one service node connection; - Filter has one service node connection AND LightPush protocol has one service node connection.
- LightPush protocol has one service node connection;
- sufficiently healthy: - sufficiently healthy:
- Filter 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.
- 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 ### Peers and connection management