this post was submitted on 12 Jun 2023
950 points (100.0% liked)
Technology
37727 readers
62 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This makes a lot of sense to me (as an Operations Engineer).
I could imagine the architecture team has low watermark triggers to rescale the architecture, kill and restore hosts, or other changes based on expected user load. When that load just.. isn't there, the automated tooling just loops the same actions causing site instability.
I've had similar issues before, so it seems like a feasible explanation