fix: Reduce Gitea runner request frequency to prevent DDoS-like behavior
- Increase fetch_interval from 2s to 10s to reduce load on Gitea - Increase fetch_timeout from 5s to 30s for better error handling - Add documentation about runner overloading Gitea and how to fix it - Prevents 504 errors caused by runner bombarding Gitea with requests
This commit is contained in:
@@ -90,3 +90,17 @@ cd deployment/gitea-runner
|
||||
- Prüfe Traefik-Logs: `docker logs traefik`
|
||||
- Stelle sicher, dass Gitea nicht überlastet ist
|
||||
|
||||
**Runner überlastet Gitea (DDoS-ähnliches Verhalten):**
|
||||
- Der Runner kann Gitea mit zu vielen Anfragen überlasten, besonders bei Fehlern
|
||||
- **Lösung**: `fetch_interval` in `config.yaml` erhöhen (Standard: 2s → Empfohlen: 10s oder mehr)
|
||||
- **Lösung**: `fetch_timeout` erhöhen (Standard: 5s → Empfohlen: 30s)
|
||||
- **Sofortmaßnahme**: Runner deaktivieren/stoppen, bis Gitea wieder stabil ist:
|
||||
```bash
|
||||
cd deployment/gitea-runner
|
||||
docker compose stop gitea-runner
|
||||
```
|
||||
- Nach Anpassung der Konfiguration Runner neu starten:
|
||||
```bash
|
||||
docker compose up -d gitea-runner
|
||||
```
|
||||
|
||||
|
||||
Reference in New Issue
Block a user