Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 35 posts

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#12

Post by kjaftaedi »

BillinghamJ wrote: post #8
osipovas wrote: post #2

Maybe AWS US East is going to be the region with random failures? "I want to have an AWS region where everything breaks with high frequency" https://news.ycombinator.com/item?id=24103746

It always has been - us-east-1 is the biggest region by far, so scale problems tend to arise there first.

All updates and patching start with us-east-1.

The main reason it has the most issues is because it's the guinea pig for production update deployments.

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#16

Post by whoevercares »

kjaftaedi wrote: post #12
BillinghamJ wrote: post #8

Earlier quoted context omitted.

It always has been - us-east-1 is the biggest region by far, so scale problems tend to arise there first.

All updates and patching start with us-east-1. The main reason it has the most issues is because it's the guinea pig for production update deployments.

Hmm that’s not true, nowadays most new things will start with small regions, typically us-east-2

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#17

Post by bognition »

gonehome wrote: post #14

Yes - I've been seeing failures this morning. Searched around didn't see much on twitter beyond this: https://twitter.com/Flock/status/1294304262126804993?s=20 We think it's one AZ in us-east-1.

yeah this is very similar to what we're seeing. We reached out to AWS for help and they reported issues on their side but didn't go into greater details.

we've been seeing issues like this on and off for a few weeks now.

Re: Ask HN: Has anyone else seen TCP connection issues in AWS US East this week?

#18

Post by gregmac »

WaxProlix wrote: post #10
sudhirj wrote: post #9

Earlier quoted context omitted.

Each account's AZ codes point to a different AZ—it's a way of avoiding conversations like this where people think a particular AZ is better than others.

That's no longer the case, except in legacy regions (which IAD is); I think there's a reconciliation mechanism though in those cases.

Can you cite something about this? I can't find anything, except confirming that's not true [1].

Your profile says you work at AWS so I assume you have inside info on this. Perhaps you could also explain why this change would get made? I always considered it pretty smart to do - With consistent machines, wouldn't the lowered-lettered zones get significantly more traffic? Most of my deploys go to a+b or a+b+c (and I have various services running in 5 different regions, I think). I'm not sure I even have anything running in more than 3 AZs, and thus never use AZ d, for example. I'm positive I'm not alone in that style of setup.

----

EDIT: Just comparing two accounts I have (which are linked, if that makes a difference), it does in fact look like most regions do have the same mappings. us-east-1 and us-west-2 are definitely different, but all the other ones I checked seem to be the same. They're not all consistent (a=1, b=2, etc) though, but for example, these are the same on both accounts:

    AZ Name         AZ ID
    eu-central-1a   euc1-az2
    eu-central-1b   euc1-az3
    eu-central-1c   euc1-az1
    eu-west-3a      euw3-az1
    eu-west-3b      euw3-az2
    eu-west-3c      euw3-az3
    ap-south-1a     aps1-az1
    ap-south-1b     aps1-az3
    ap-south-1c     aps1-az2
I still find this silly. Anyone following basic examples or deploying single-AZ is going to provision stuff in the "a" zone. That zone must be 10x bigger than "c" in any given region. It blows my mind.

[1] https://aws.amazon.com/premiumsupport/knowledge-center/vpc-m...

Post reply on HN