Slack’s Incident on 2-22-22
slack.engineering
Slack’s Incident on 2-22-22
1–10 of 183 posts
Re: Slack’s Incident on 2-22-22
#2A post-mortem with non-ISO dates? Even on THAT date?! :)
Re: Slack’s Incident on 2-22-22
#3Which 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.
Re: Slack’s Incident on 2-22-22
#4McRib is a hilarious name for a service
Re: Slack’s Incident on 2-22-22
#5A post-mortem with non-ISO dates? Even on THAT date?! :)
looks unambiguous to me lol
Re: Slack’s Incident on 2-22-22
#6McRib is a hilarious name for a service
I certainly wouldn't trust it's availability.
(The original McDonald's McRib sandwich is well known for only being sold a limited time.)
So "Mcrouter" comes from Memcache-Router, then the obvious McDonalds jokes are made and someone cleverly suggests "Mcrib" for the next service. But I can't think what the backronym would be for it. Memcache Ring Buffer maybe. Or Broker.
Re: Slack’s Incident on 2-22-22
#7An over communication platform should have scheduled outages like this regularly!
Re: Slack’s Incident on 2-22-22
#8An over communication platform should have scheduled outages like this regularly!
No post body was provided.
Re: Slack’s Incident on 2-22-22
#9A Date that is both a Palindrome and an Ambigram:
https://www.jagranjosh.com/general-knowledge/22-02-2022-is-b...