Live data from Hacker News

Slack’s Incident on 2-22-22

slack.engineering

141–150 of 183 posts

Re: Slack’s Incident on 2-22-22

#141
post #136

Which major outage ? According to the Slack uptime, there was barely 1.5 hour of outage :-) P.S. Yes I know the uptime is decide by committee, and doesn't reflect reality. I am just being cynical.

1.5 hours for a tool like Slack is major. Lots of productivity lost (or gained depending on how you view Slack) and thus $ impacts at companies that heavily rely on Slack for internal/team comms

tell that to Atlassian

Re: Slack’s Incident on 2-22-22

#142

Earlier quoted context omitted.

The complaint isn't about the particular other order, but the fact that the order is ambiguous. In this case that doesn't matter, but often it does. Americans memorize inches and yards, and often also memorize centimeters and meters, and working with either is fine, but we're not so often faced with numbers where it might be inches or centimeters and we have to figure out which (and when we are, it's sometimes a pain…

I instinctively felt that the ambiguity ought to not truly exist, but I wanted to find some backing. According to this: https://en.wikipedia.org/wiki/Date_format_by_country … all the major predominantly English speaking counties will use mostly hyphens in the dd-mm-yyyy format. So although there is ambiguity, it’s easily resolved by picking that as the default mentally and only back tracking on failure. Now in the mo…

Even people in non-English-speaking countries write in English all the time, especially on the Internet.

Picking one default and back-tracking on failure really isn't that comforting nor the constant reminder that the date you thought it was might be something else.

Re: Slack’s Incident on 2-22-22

#143
post #120
post #70

Earlier quoted context omitted.

The fact that the current top comment thread is quibbling about the date format in the title seems to agree with this assessment, if there was anything real to complain about that’s what we’d be seeing, instead we get bikeshedding on the date format in the title of a post.

[adds "bikeshedding" to vocabulary.]

Today is your lucky day!

https://xkcd.com/1053/

Re: Slack’s Incident on 2-22-22

#144

Great post mortem, I love reading these. Its pretty neat that the tech industry is relatively transparent about these situations -- we all benefit from learning about them.

As someone that spend far too much time in incident report from all kind of industry, you made my day.

I am really happy you think so. But no. We are really not transparent about them. At all.

Re: Slack’s Incident on 2-22-22

#145
post #66

Just my personal take, I think this is a really well-written incident postmortem. It's specific, extensive, candid, and dare I say, entertaining? Many incident reports are fully lacking in any meaningful detail, or wholly unapologetic. I actually enjoyed learning tidbits about the author, in particular their mention of https://how.complexsystems.fail/ . Reading this boosted my confidence in Slack's teams, which shoul…

Laura Nolan is a gem that Slack is lucky to have.

Re: Slack’s Incident on 2-22-22

#146

Tidbit: 2-22-22 was also when Russia invaded Ukraine And Joe Bidens statement about the invasion was on 2-22-22 2:22pm on the dot. I could not figure out the significance of this more than 11:11 was when WW1 ended, but it's probably something else.

Nope, you’re off by two days: https://en.wikipedia.org/wiki/2022_Russian_invasion_of_Ukrai...

It was the announcement of invasion. 22-2-22

Then Biden did a speech against on 2:22 22-2-22

The actual war started in 2014

Re: Slack’s Incident on 2-22-22

#147

Tidbit: 2-22-22 was also when Russia invaded Ukraine And Joe Bidens statement about the invasion was on 2-22-22 2:22pm on the dot. I could not figure out the significance of this more than 11:11 was when WW1 ended, but it's probably something else.

Nope, you’re off by two days: https://en.wikipedia.org/wiki/2022_Russian_invasion_of_Ukrai...

To refresh your memory

https://edition.cnn.com/europe/live-news/ukraine-russia-news...

Re: Slack’s Incident on 2-22-22

#148
I am confused by the query that had the problem. Specifically, I am confused by why the sharding is done by user id.

Even the largest Slack instance probably has under 100,000 users and less than 1000 peak messages per second. That feels to me like it could be served by a single master DB. It feels like that would be a better way to shard.

Major downside is the major difference in shard sizes so some management/migration might be needed but it seems doable to me.

Certainly it feels naively that scaling should be easy due to the way slack instances are independent (unlike say Twitter).

Re: Slack’s Incident on 2-22-22

#149

I am confused by the query that had the problem. Specifically, I am confused by why the sharding is done by user id. Even the largest Slack instance probably has under 100,000 users and less than 1000 peak messages per second. That feels to me like it could be served by a single master DB. It feels like that would be a better way to shard. Major downside is the major difference in shard sizes so some management/migra…

Workspaces are not completely independent, such as for the Slack Connect feature. Some more details here: https://slack.engineering/scaling-datastores-at-slack-with-v...

Re: Slack’s Incident on 2-22-22

#150

Earlier quoted context omitted.

which only makes it confusing for the rest of the world

It's not that confusing if you know there are only 12 months. If it happened to occur on 2-4-22, then it would be pretty confusing.

its particularly bad because US dates are written with slashes. please leave dashes for ISO so we have some hope of understanding anything.
Post reply on HN