EventHub/EventHubBack
3
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(mnesia): поднять dump_log_write_threshold; Traefik base v3.3.6. Refs EventHub/EventHubBack#34 Refs EventHub/EventHubDevOps#3 [skip ci]

Browse Source
This commit is contained in:
Aleksey Sabilin
2026-07-15 17:28:39 +03:00
parent f7f0038556
commit 94106cf964
4 changed files with 34 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/tsung/README.md
+2
View File
@@ -62,6 +62,8 @@ IFT = Docker Swarm **внутри WSL2 на Windows**. Aggressive open-loop бе
**Controlled hold ×3** (`20260715-1411/`, `EVENTHUB_REPLICAS=3`): connect по фазам 0.2→0.035 GREEN (0.05 mean≈40 ms); overall BOUNDARY_HIT из‑за **3772× HTTP 429** — узкое место сместилось на Traefik `api-ratelimit` (per source IP, было 5000/1m≈83 rps). После поднятия IFT-лимитов до 2000/1s (EventHubBack#32) перепроверить hold ×3.
Под hold также: `Mnesia is overloaded: {dump_log, write_threshold|time_threshold}`. Краткосрочно: `MNESIA_DUMP_LOG_WRITE_THRESHOLD` (IFT default 50000, EventHubBack#34). Долгосрочно: меньше sync-транзакций / hot-path вне Mnesia.
Restore fallback: оркестратор → WSL SSH, при fail Windows `restore-ift.ps1`.
Если после stress SSH «висит на banner» — **reboot IFT**, затем: