commit cd687a0a2c430efac0bf98dcc837c3809a63c52b
parent 0e81e2114adb16787d865e2f658183c9b5abdd23
Author: teor <teor2345@gmail.com>
Date: Tue, 16 May 2017 18:06:05 +1000
Update fallback stability requirements
Decrease the minimum number of fallbacks to 100.
Final fix to 20913.
Diffstat:
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/changes/bug20913 b/changes/bug20913
@@ -1,7 +1,9 @@
o Minor bugfixes (fallbacks):
- Make sure fallback directory mirrors have the same address, port, and
relay identity key for at least 30 days before they are selected.
- Partial fix to 20913, bugfix on 0.2.8.1-alpha.
+ Fixes 20913, bugfix on 0.2.8.1-alpha.
- Decrease the guard flag average required to be a fallback. This allows
us to keep relays that have their guard flag removed when they restart.
- Partial fix to 20913, bugfix on 0.2.8.1-alpha.
+ Fixes 20913, bugfix on 0.2.8.1-alpha.
+ - Decrease the minimum number of fallbacks to 100.
+ Fixes 20913, bugfix on 0.2.8.1-alpha.
diff --git a/scripts/maint/updateFallbackDirs.py b/scripts/maint/updateFallbackDirs.py
@@ -198,7 +198,7 @@ FALLBACK_PROPORTION_OF_GUARDS = None if OUTPUT_CANDIDATES else _FB_POG
# Limit the number of fallbacks (eliminating lowest by advertised bandwidth)
MAX_FALLBACK_COUNT = None if OUTPUT_CANDIDATES else 200
# Emit a C #error if the number of fallbacks is less than expected
-MIN_FALLBACK_COUNT = 0 if OUTPUT_CANDIDATES else MAX_FALLBACK_COUNT*0.75
+MIN_FALLBACK_COUNT = 0 if OUTPUT_CANDIDATES else MAX_FALLBACK_COUNT*0.5
# The maximum number of fallbacks on the same address, contact, or family
# With 200 fallbacks, this means each operator can see 1% of client bootstraps