khrystoph

4 ms·

1.
by khrystoph 2y ago
yeah, AWS rarely has significant capacity issues. While the capacity utilization typically sits around 90% across the board, they're constantly landing new capacity, recovering broken capacity, and working to fix issues that cause thin
2.
by khrystoph 2y ago
That's happened several times, actually. That's probably just the latest one. The really fun one was when S3 went down in 2017 in Virginia. Caused global outages of multiple services because most services were housed out of Virgin
3.
by khrystoph 2y ago
Netflix big? Bigger or Smaller? I'm betting I have a good idea of one of the possible orgs you work for, since I used to work specifically with the largest 100 customers during my ~3yr stint in premium support
4.
by khrystoph 2y ago
yeah, I agree. I think most places will at least keep it until the existing contract comes time for renegotiation and most will probably keep using cs. It's far easier for IT departments to just keep using it than it is to switch and m
5.
by khrystoph 2y ago
>This is absurd. Every BMC I’ve ever used has an option to turn off the power immediately. Every low level hypervisor can do this, too. (Want a QEMU guest gone? Kill QEMU.). Why on Earth can’t public clouds do it? The issue is far more n
6.
by khrystoph 2y ago
There is a way with AWS, but it carries risk. You can force detach an instance's volume while it's in the shutting down state, but if you re-attach it to another machine, you risk the possibility of a double-write/data corrup