3 ms·
Sorry the 2015 one. I misremembered the year https://aws.amazon.com/message/5467D2/ https://aws.amazon.com/message/5467D2/ I imagine this was impossible in 20
by julianozen 1y ago
Sorry the 2015 one. I misremembered the year
https://aws.amazon.com/message/5467D2/ https://aws.amazon.com/message/5467D2/
I imagine this was impossible in 2017 because of actions taken after the 2015 incident
- planckscnst 1y agoDefinitely impossible in 2015. If you're talking about this part: > Initially, we were unable to add capacity to the metadata service because it was under such high load, preventing us from successfully making the requisite administrative requests. It isn't about spinning up ec2 instances or provisioning hardware. It is about logically adding the capacity to the system. The metadata service is a storage service, so adding capacity necessitates data movement. There are a lot of things that need to happen to add capacity while maintaining data correctness and availability (mind at this point, it was still trying to fulfill all requests)
- julianozen 1y agoI’m referring to impact on other services