I upgraded our site last week from 3.2.0.beta4-dev to 3.3.0.beta3. (Yesterday I updated to 3.3.0.beta5-dev) All was fine until I enabled the reactions like sync setting (see image below). From that point on, the server appears to have been busy processing the reactions, and users are getting 502 errors and many requests are not being handled properly. Some threads aren’t marked as being read, they aren’t able to post randomly, etc. Is there any way to see how far along the retroactive background process is so we know when this behavior will (hopefully) return to normal? Or any updates to handle this better? Or slow it down so it doesn’t impact site performance? Or is this unrelated and just a coincidence? Also of note: the site has 2.4M posts and around 2M likes. [The image shows several line graphs displaying system resource usage metrics over time, including CPU utilization percentage, load average, memory usage percentage, and disk I/O activity. (Captioned by AI)]

FYI @martin Not sure if you ran across anything like this when enabling for the hosted sites? [תמונה] Changes to which reactions thumbsup are counted as likes heart megaphoneAnnouncements Announcement rocket I would like to announce that we are going to start rolling out the discourse_reactions_like_sync_enabled setting to all of our hosted sites, setting it to true, and setting it to default true for new sites. What this means is that historical reactions will have a Like record created for them. On some sites that haven’t used reactions this may be a very small amount, on other sites this may be to the tune of tens of thousands of records. This will influence the Top and Ho…

Following up on this .. is there any way to see the progress / remaining items in this? I updated the ScheduledLikeSynchronizer to run every '0,30 4-10 * * *' (only overnioght) instead of every 1.hour (constantly) but it doesn’t appear to be working; is that cron notation available? I’m trying to let this continue to run, but not interfere with our user’s ability to use the site.

I don’t know if you were able to fix it, but in our case we also have a lot of posts and likes. For now, we have opted to disable the Discourse reactions like sync because it was causing those CPU peaks every 60 minutes and a lot of 502 errors. [The image displays a time-lapse of CPU usage for a 'ys' and 'user' context, with noticeable fluctuations in both before and after enabling synchronization for 'Discourse reactions' between 15:00 and 21:00. (Captioned by AI)]

תגובות כמו בעיות סינכרון

תמיכה

Brandon_Martus (Brandon Martus) 23 בפברואר,‏ 2025,‏ 9:39pm 6

Nope. We just ended up turning off that setting.

נושא		תגובות	צפיות
ReactionLikeSynchronizer reprocesses already-trashed PostAction likes every hour Bug	2	234	15 באוקטובר,‏ 2026
Changes to which reactions :thumbsup: are counted as likes :heart: Announcements reactions	46	3311	27 במאי,‏ 2024
Reactions plugin: 500 Internal Server Error Bug reactions	8	695	25 באוקטובר,‏ 2022
Server Performance Issues Due to High CPU Usage Product Support	5	457	23 בפברואר,‏ 2025
Real-time updating of topics freezes under high activity Product Support	89	9049	26 בפברואר,‏ 2022

תגובות כמו בעיות סינכרון

נושאים קשורים