5 ms·
Cpu0 : 0.3%us, 0.0%sy, 0.0%ni, 0.0%id, 99.7%wa, 0.0%hi, 0.0%si, 0.0%st <-- EBS subsystem is completely unreachable. I/O wait times are tanked across th
by stevefink 14y ago
Cpu0 : 0.3%us, 0.0%sy, 0.0%ni, 0.0%id, 99.7%wa, 0.0%hi, 0.0%si, 0.0%st <-- EBS subsystem is completely unreachable. I/O wait times are tanked across the board for me (I'm in US-EAST-1).
- nirvdrum 14y agoWhat zone? I really wish Amazon would provide that info, instead of saying that it only affects one zone.
- stevefink 14y agoBoth my MySQL master (I'm not using RDS) and Redis Master servers are affected and are located in zone us-east-1a.
- kokon 14y agoWhy do you have two masters in the same AZ?
- gabrtv 14y agoAFAIK zones are randomized. 1a for me is 1d for you.
- stevefink 14y agoThat's really interesting if it's true. I had never heard this before. Thanks for the tip.
- mattwdelong 14y agoDo you know why this is?
- gdb 14y agoSupposedly it's for load-balancing purposes. (Most people spin up their machines in 1a.)
- lytfyre 14y agoHumans are predictable - it wouldn't spread the load across zones very well.
- blantonl 14y agoprobably to prevent folks from all stacking up in a single AZ. Just think if someone posted a blog post saying "I've noticed that EBS performance is far better in 1d vs. 1a"
- nirvdrum 14y agoWell, they also return errors if a zone is out of capacity. That seems like it would guard against the issue a bit. But maybe they just don't want to have to field loads of questions about that.
- iharris 14y agoYeah, for me, 1d experiences the lowest load of all zones. According to the pricing history for spot instances, 1d experiences the fewest price spikes compared to 1a and 1b. I'd be interested to see if other users have noticed the same thing for their zones.
- biot 14y agoI find that random(5) is the best performing. For okay but consistent performance, random(5) is decent, but you should definitely avoid random(5) due to high load.
- dwhsix 14y agoI believe it's also a security measure.
- RKearney 14y agoIt was done due to badly written tools and scripts firing up instances in Availability Zone A every time.
- nirvdrum 14y agoAhh. Now that you mention it, I think I recall reading that before. It struck me as weird though because 1a was obviously the first one and 1e was recently added. So, would they rebalance my labels in that case?
- deleted 14y ago[deleted]
- aaronharder 14y agoUnfortunately, there is no meaningful way for them to say which zone because zone labels are different for each user.
- zedwill 14y agoIt is affecting me on US-EAST-1B
- iharris 14y agoI have instances in two different zones - both are down, although I don't know if AWS's randomization means that my 1a and 1d are actually located in the same logical zone.
- res0nat0r 14y agoThe zones map differently per account, but if you've launched instances in different zones for your same account you are for sure in different AZ's.