Ошибка 502 / Unicorn Timeout на странице Rewind для высокоактивных пользователей

martin · 02.Январь.2026 02:04:28

I think this fix should help:

github.com/discourse/discourse

FIX: Only actually fetch initial report count in Rewind

main ← fix/rewind-initial-report-count

merged 11:34PM - 04 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.

Тема		Ответов	Просм.
Timeouts on large, old forum Support	11	948	27.05.2022
Users reporting lots of 502 errors when attempting to post due to "max consecutive replies" check Bug	37	2928	18.01.2019
502 error while opening some user profiles Bug	18	571	27.05.2024
Errors in /logs since the latest update Support	4	137	01.09.2024
Workers / MiniRacer::ScriptTerminatedError timeouts in /logs Support	6	133	03.04.2025

Ошибка 502 / Unicorn Timeout на странице Rewind для высокоактивных пользователей

Связанные темы