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

AWS us-east-1 down

news.ycombinator.com

Post reply on HN
Print view View original

261–270 of 331 posts

Re: AWS us-east-1 down

#261

Post by dathinab »

perlgeek wrote: post #107
kroltan wrote: post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

It's also not too complicated to add a few lines of javascript that show the datet/time in the user's local time zone (via Date.getTimezoneOffset) as well.

still show the timezone it's displayed in, users aren't always fully aware of which time zone their browser is believing they are in (sounds stupid at first but imagine you just traveled somewhere and are temporary used to that time zone but e.g. your laptop is fixed set to your home time zone, or maybe it's not and you just thought it is, or maybe you are just a bit confused because you switched time zones 4 times the last 24 hours etc.)

Re: AWS us-east-1 down

#263

Post by nfRfqX5n »

> At that time, we began processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services. As of 3:37 PM, the backlog was fully processed

pretty cool that stuff was stored in a backlog and eventually processed!

Re: AWS us-east-1 down

#264

Post by yen223 »

dylan604 wrote: post #66
kroltan wrote: post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

just report it in epoch seconds

Just make sure not to confuse it with epoch milliseconds!

Re: AWS us-east-1 down

#265

Post by dathinab »

dylan604 wrote: post #66
kroltan wrote: post #60

Earlier quoted context omitted.

Semi-related: if you ever feel the need to report times to a global audience, not only make sure to always report the timezone (even if it is the same as the user's), but also use UTC offsets rather than timezone names. Life is too short to remember what each timezone name means and converting to it, UTC offsets are much easier on the mental calculator.

just report it in epoch seconds

better:

time encoded as a float of trecenti-seconds since year -8435 of the Georgian Calendar

why?

'caus it hurt to even just think about implementing that anywhere

Re: AWS us-east-1 down

#266

Post by capableweb »

nfRfqX5n wrote: post #263

> At that time, we began processing the backlog of asynchronous Lambda invocations that accumulated during the event, including invocations from other AWS services. As of 3:37 PM, the backlog was fully processed pretty cool that stuff was stored in a backlog and eventually processed!

I don't want to diminish anything, but in terms of dealing with queues, backlogs are pretty much a basic requirement from the beginning.

Re: AWS us-east-1 down

#267

Post by sk0g »

inopinatus wrote: post #201
TremendousJudge wrote: post #68

Earlier quoted context omitted.

It's also usually extremely US-centric. Nobody outside of North America has any idea what "PDT" or "Mountain Time" means.

Unnecessary reflux obtained during US-Australian collaboration from insufficiently specific references to "east coast time".

Even in Australia, AEST has a DST flavour and a non-DST one. Queensland does not observe DST while the other states do. You can drive around a roundabout at the border and switch timezones for fun. Or go down there to celebrate the new year twice.

Or go from rabbits being OK to some 5 figure fine if you're caught with one :)

Re: AWS us-east-1 down

#268

Post by OJFord »

throw03172019 wrote: post #252

My Whole Foods grocery pickup order was affected by this outage. They couldn’t check me in. Groceries were packed in the fridge but they told me to come back later. What a waste of time.

Are you just guessing it's related or is there a reason to be sure? Either way, does seem sjll6 to have no manual fallback 'check-in' (or policy-level ability to bypass the need for it) mechanism.

Re: AWS us-east-1 down

#270

Post by klysm »

hosteur wrote: post #250
klysm wrote: post #239

Earlier quoted context omitted.

Even if people _do_ care, there isn't much to do about it.

If people do care they could use other hosting providers such as Hetzner or OVH, no?

The economics of the situation make it so that at your job that's not very realistic.
Post reply on HN