502 Fehler / Unicorn Timeout auf der Rewind-Seite für sehr aktive Benutzer

martin · 2. Januar 2026 um 02:04

Ich denke, dieser Fix sollte helfen:

github.com/discourse/discourse

FIX: Only actually fetch initial report count in Rewind

main ← fix/rewind-initial-report-count

opened 01:07AM - 02 Jan 26 UTC

martin-brennan

+265 -143

We changed rewind to fetch reports in batches, fetching only 3 to start with, an…d then fetching more as needed. However, we were actually fetching all reports server side then cutting down the results to only 3, which meant we were incurring unnecessary load on the server in the case where reports were not cached, leading to 502 errors in some cases. This fix also necessitates changing the caching strategy. Previously, we would cache all of the reports at once then when fetching an individual report we would pull from there. However now that we aren't fetching all reports at once, we need to cache individual reports and fetch them if they are not cached.

Thema		Antworten	Aufrufe
Timeouts on large, old forum Support	11	934	27. Mai 2022
Users reporting lots of 502 errors when attempting to post due to "max consecutive replies" check Bug	37	2854	18. Januar 2019
502 error while opening some user profiles Bug	18	537	27. Mai 2024
Workers / MiniRacer::ScriptTerminatedError timeouts in /logs Support	6	117	3. April 2025
502 Bad Gateway for only two Topics Installation arm	20	1782	17. November 2022

502 Fehler / Unicorn Timeout auf der Rewind-Seite für sehr aktive Benutzer

Verwandte Themen