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

Slack is down

status.slack.com

Post reply on HN
Print view View original

581–590 of 840 posts

Re: Slack is down

#581

Post by godot »

agrippanux wrote: post #152
exhaze wrote: post #136

Earlier quoted context omitted.

I haven't worked at Slack, so I can't speak with high confidence. A traffic spike is a possible reason, but I'm willing to bet that it's not the reason: > Doubt anyone releasing big changes Monday morning. This is definitely an engineering best practice, and by best practice, I mean something that Uber's, I mean Slack's SRE team strongly pushed for, and got politely overruled on. After a code freeze is lifted, it's q…

In my experience it's not promotion-eager engineers that want to push after a code freeze, it's antsy product managers. YMMV tho.

IMO it really doesn't have to be promotion-eager engineers or antsy product managers. I'm fairly satisfied with my role and comp and work type with where my career/life-stage is. I just did a code release first thing this morning, not because I am promotion-eager, but just because I'm picking back up where I left off, like any normal day. Granted I work at a much smaller company than Slack with orders of magnitude less traffic.

Re: Slack is down

#582

Post by igetspam »

kmichler wrote: post #292

We're using Google Chat again. Feels ancient. https://chat.google.com/

If you're using gsuite already, it's a usable failover. I send all my alert notifications there, as a fallback already. Dragging people in was trivial. It's better than the group SMS that one person tried to use.

Re: Slack is down

#584

Post by bob1029 »

offtop5 wrote: post #521

Like human beings, can we all imagine that every single service can have a couple of off days a year.

The entire point of all of the engineering we talk about around here is to produce services with inhuman capabilities and resilience.

Re: Slack is down

#585

Post by politelemon »

adrianpike wrote: post #310
kmichler wrote: post #292

We're using Google Chat again. Feels ancient. https://chat.google.com/

Same - and it's just... weird. The "everything must be in a thread" model feels really clunky.

Subjective... I've found Slack and co's interspersed conversations far too chaotic, and temporal; threading is a great way of organising many different concurrent topics.

And to be clear I don't mean Slack's implementation of threads which is hiding it away in a separate panel and which doesn't get used by everyone either.

Re: Slack is down

#586

Post by AnIdiotOnTheNet »

oriettaxx wrote: post #552

I am so glad that at least today I do not hear that slak annoying sound. I do really think Slack is not helping me, at all, to concentrate on my job (system administrator): synchronous messages are really the worst, ever, while working: email is much much better

Honestly I'm fairly sure the vast majority of "technology" we've deployed, as an industry, in the past 10-15 years has actively made life worse. I don't know about anyone else, but that's the opposite of why I got into technology.

Re: Slack is down

#587

Post by Spivak »

arpa wrote: post #478
daniellarusso wrote: post #467

Earlier quoted context omitted.

Maybe my DevOps folks should not be privy to all internal communications? That is one reason we did not go with Mattermost.

If you do not trust your own devops, why are you trusting someone elses devops?

We structure our company similarly. With effort DevOps is god on everything except HR, Sales, Finance, Chat, and C-level management which are operated with 3rd party services controlled by the individual departments and "owned/managed" by the C-suite.

Re: Slack is down

#588

Post by NewEntryHN »

exhaze wrote: post #89

When I was at Uber, we noticed that most incidents are directly caused by human actions that modify the state of the system. Therefore, a large "backlog" of human actions that modify the system state have a much higher chance of causing an incident. My bet is that this incident is caused by a big release after a post-holiday "code freeze".

Another common cause is resource exhaustion as a result of poorly monitored resources (or bugged monitoring). For example Google's authentication was down because their system reported (wrongly) available quota of 0. The last two incidents at my company were also related to resource exhaustion.

Re: Slack is down

#589

Post by tayo42 »

manquer wrote: post #568
erk__ wrote: post #374

Earlier quoted context omitted.

It is easier to cache stuff for users who are not logged in as it is the same for everyone. and everyone is looking up on Hackernews at the moment to see what is wrong with slack, which is probably the cause of the slowness.

While it is true for most applications. HN does not do any customisation of the content. I don't notice I am not logged in until commenting

You would cache the rendered html, the front page has your username and points and stuff. The whole page will be unique to you because of that

Re: Slack is down

#590

Post by deepakhj »

boie0025 wrote: post #333
daze42 wrote: post #115

Earlier quoted context omitted.

Availability zones are unique for each account. So my zone A could be your zone C, for example.

I never knew this, but I think it makes sense. Is there any documentation that explains why this is the case? I suspect it is to distribute bias to the first option, but I'd love to read about it. [edit] Nevermind, I just needed the right combination of terms to find it: https://docs.aws.amazon.com/ram/latest/userguide/working-wit...

This is so everyone doesn't launch in one zone, "us-east-1a".
Post reply on HN