• DougPiranha42@lemmy.world
    link
    fedilink
    English
    arrow-up
    54
    arrow-down
    16
    ·
    15 hours ago

    Interesting. A client side bug causes server-level overload but only after unrelated changes gradually make the problem worse. Rerouting traffic to healthy servers overloads those too and spreads the outage. The client code surely “worked on my computer” lol

      • DougPiranha42@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        I guess I misunderstood it.

        Inside an internal Windows process, competing tasks were waiting for access to shared resources, a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity.

        I read this as the behavior that precipitated the issue on the gateway was caused by how Windows sent traffic to exchange servers. So by Windows they mean whatever is running on the gateway?

      • threeonefour@piefed.ca
        link
        fedilink
        English
        arrow-up
        43
        arrow-down
        2
        ·
        15 hours ago

        It says multiple times that the issue was with Microsoft’s internal cloud server software, not Windows.

        The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers.

        The failure was within Microsoft’s cloud infrastructure, not customer Windows systems

        • eleijeep@piefed.social
          link
          fedilink
          English
          arrow-up
          7
          ·
          edit-2
          9 hours ago

          Yeah exactly, I don’t understand how the original comment is still getting upvotes.

          Since your comment it gained (+36, -11). People don’t read, I guess.