There was another attack going on (as you might have noticed). We’re working on a fix. In the meantime, we’ve blocked the listing of comments, so we at least aren’t down, but it did break comments.
Hope to have a fix in the next hour. Stay tuned!
Update OK we’ve implemented a fix, again many thanks to @sunaurus@lemm.ee for his assistance. This will prevent the outages we’ve seen last couple of days. Let’s see what they will come up with next…
@ruud@lemmy.world and @sunaurus@lemm.ee
I added some self-awareness of concurrency to the Lemmy API Rust logic: https://github.com/LemmyNet/lemmy/pull/3805/files - this should allow a more standard in-band response to concurrency slow-response server overloads. Keywords (‘woodstocksnoopy’ as watchdog, and even more alarming keyworld to find in your logs: ‘SITE_OVERLOAD’) were added to the logging to make it explicit when this is happening.