Skip to content

Commit 4566810

Browse files
authored
docs(faq): Add initial details about penalties
Ad discussed on Slack, and related to cronian-tech/saturn-moonlet#3. Signed-off-by: Michael Vorburger ⛑️ <[email protected]>
1 parent 4292ce7 commit 4566810

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

docs/faq.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,21 @@ These are the current penalties that affect both DNS weight and earned FIL:
6060
- Fraudulent logging (e.g. self-dealing)
6161
- Multi-noding (Running multiple nodes on the same host)
6262

63+
These are visibile e.g. by hovering over the _Weight_ of a Node on https://dashboard.saturn.tech, or on the _Penalty_ graph of the [Moonlet](https://github.com/31z4/saturn-moonlet).
64+
65+
Here are more details about each kind of penalty, with information what could cause it, and how to remedy if your Node encounters them:
66+
67+
- `error_ratio` is caused by errors as shown in the log of L1 Node container, scuh as:
68+
- Node refusing to connect with a client multiple times.
69+
- `dup_cache_miss_ratio` is caused if a computed error ratio for consecutive duplicate cache misses goes over a threshold.
70+
- `health_check_failures` are caused by an unexpectedly (not deregistered) unreachable node.
71+
- This penalty starts with each health check failure event, and then gradually decreases over ~6h.
72+
- Fix this by resolving the root cause of the node unavailability.
73+
- Note the [deregister my node](#how-can-i-manually-deregister-my-node) section.
74+
75+
None of these are "expected" under normal operation, and all are something that you want to keep down.
76+
77+
6378
## Registration
6479

6580
### My Node fails to register with error ETIMEDOUT/EHOSTUNREACH

0 commit comments

Comments
 (0)