aboutsummaryrefslogtreecommitdiff
path: root/proposals/328-relay-overload-report.md
diff options
context:
space:
mode:
Diffstat (limited to 'proposals/328-relay-overload-report.md')
-rw-r--r--proposals/328-relay-overload-report.md10
1 files changed, 5 insertions, 5 deletions
diff --git a/proposals/328-relay-overload-report.md b/proposals/328-relay-overload-report.md
index 5901b93..bdb4fec 100644
--- a/proposals/328-relay-overload-report.md
+++ b/proposals/328-relay-overload-report.md
@@ -41,16 +41,16 @@ state" which can be one or many of the following load metrics:
- Any OOM invocation due to memory pressure
- Any ntor onionskins are dropped
- [Removed in tor-0.4.6.11 and 0.4.7.5-alpha]
+ \[Removed in tor-0.4.6.11 and 0.4.7.5-alpha\]
- A certain ratio of ntor onionskins dropped.
- [Added in tor-0.4.6.11 and 0.4.7.5-alpha]
+ \[Added in tor-0.4.6.11 and 0.4.7.5-alpha\]
- TCP port exhaustion
- DNS timeout reached (X% of timeouts over Y seconds).
- [Removed in tor-0.4.7.3-alpha]
+ \[Removed in tor-0.4.7.3-alpha\]
- CPU utilization of Tor's mainloop CPU core above 90% for 60 sec
- [Never implemented]
+ \[Never implemented\]
- Control port overload (too many messages queued)
- [Never implemented]
+ \[Never implemented\]
For DNS timeouts, the X and Y are consensus parameters
(overload_dns_timeout_scale_percent and overload_dns_timeout_period_secs)