Erreur 502 / Timeout Unicorn sur la page Rewind pour les utilisateurs très actifs

martin · Janvier 2, 2026, 2:04

Je pense que cette correction devrait aider :

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.

Sujet		Réponses	Vues
Timeouts on large, old forum Support	10	999	Mars 27, 2019
Users reporting lots of 502 errors when attempting to post due to "max consecutive replies" check Bug	36	3139	Janvier 18, 2019
502 error while opening some user profiles Bug	18	622	Mai 27, 2024
Errors in /logs since the latest update Support	3	255	Août 29, 2024
Workers / MiniRacer::ScriptTerminatedError timeouts in /logs Support	6	176	Avril 3, 2025

Erreur 502 / Timeout Unicorn sur la page Rewind pour les utilisateurs très actifs

Sujets connexes