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

Salesforce Global Outage

status.salesforce.com

Post reply on HN
Print view View original

51–60 of 182 posts

Re: Salesforce Global Outage

#52

Post by fhub »

Cause: Legacy Salesforce login service got into a resource-exhaustion cascade.

Fix: Rolling some unspecified fix they proved in testing out over the fleet seemingly very slowly (After their earlier attempts to roll something out faster failed).

Details at https://status.salesforce.com/incidents/20004433

Re: Salesforce Global Outage

#54

Post by cube00 »

raffraffraff wrote: post #47

Have you tried turning it off and then on again? > We're no longer pursuing restarts as a path to remediation. Oh you have

Kind of surprised they admit they're going to try restarting and see what happens. I'm sure it happens everywhere but nobody admits it.

> We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue.

At least it didn't fix the problem so they can actually start finding the real cause.

> We're no longer pursuing restarts as a path to remediation.

Why isn't the AI they sell telling them what's wrong? Why do they need to take shots in the dark to "see if that resolves the issue"?

Re: Salesforce Global Outage

#57

Post by [deleted] »

cube00 wrote: post #54
raffraffraff wrote: post #47

Have you tried turning it off and then on again? > We're no longer pursuing restarts as a path to remediation. Oh you have

Kind of surprised they admit they're going to try restarting and see what happens. I'm sure it happens everywhere but nobody admits it. > We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue. At least it didn't fix the problem so they can actually start finding the real cause. > We're no longer pursuing restarts as a path to remediation. Why isn't the AI they sell telli…

[deleted]

Re: Salesforce Global Outage

#58

Post by andrewinardeer »

cube00 wrote: post #54
raffraffraff wrote: post #47

Have you tried turning it off and then on again? > We're no longer pursuing restarts as a path to remediation. Oh you have

Kind of surprised they admit they're going to try restarting and see what happens. I'm sure it happens everywhere but nobody admits it. > We've attempted a rolling restart on one of the impacted instances to see if that resolves the issue. At least it didn't fix the problem so they can actually start finding the real cause. > We're no longer pursuing restarts as a path to remediation. Why isn't the AI they sell telli…

"Yeah, I'm with Rob. Just let's reboot and see what happens"
Post reply on HN