Comment on Why is serveral instances down simultaneously? Is it just me?

hitagi@ani.social ⁨1⁩ ⁨year⁩ ago

• zalack@kbin.social ⁨1⁩ ⁨year⁩ ago

  It's not that strange. A timeout occurs on several servers overnight, and maybe a bunch of Lemmy instances are all run in the same timezone, so all their admins wake up around the same time and fix it.

  Well it's a timeout, so by fixing it at the same time the admins have "synchronized" when timeouts across their servers are likely to occur again since it's tangentially related to time. They're not likely to all fail again at the same moment.

  It's kind of similar to the thundering herd where a bunch of things getting errors will synchronize their retries in a giant herd and strain the server. It's why good clients will add expenses back off AND jitter (a little bit of randomness to when the retry is done, not just every x^2 seconds). That way if you have a million clients, it's less likely that all 1,000,000 of them will attempt a retry at the extract same time, because they all got an error from your server at the same time when it failed.

  source

  • hitagi@ani.social ⁨1⁩ ⁨year⁩ ago

    Interesting. Never thought of it that way.

    source
  • Blaze@iusearchlinux.fyi ⁨1⁩ ⁨year⁩ ago

    Interesting

    source
• badmin@lemm.ee ⁨1⁩ ⁨year⁩ ago

  wrong issue lol

  source

  • hitagi@ani.social ⁨1⁩ ⁨year⁩ ago

    This probably makes more sense although the issue I was experiencing earlier had similar logs as the issue I linked and others have commented on it too around the same time. I’m guessing they’re related.

    source

    • Shadow@lemmy.ca ⁨1⁩ ⁨year⁩ ago

      The original issue is just a symptom of all database threads being tied up. People just don’t know how to follow an error message to the root cause.

      The real source of the issue is db locking from triggers and cascading deletes on a major user change.

      My report in github.com/LemmyNet/lemmy/issues/3649 has the offending query.

      source

      • hitagi@ani.social ⁨1⁩ ⁨year⁩ ago

        Thanks for clarifying.

        source