Live data from Hacker News

Fly.io Status – Consul cluster outage

status.flyio.net

121–123 of 123 posts

Re: Fly.io Status – Consul cluster outage

#121
post #55

Earlier quoted context omitted.

How is this possible? How is consul not self—healing? It just seems so brittle in a way even database clusters aren’t.

All distributed decentralized systems are brittle. The only people who don't think this are people who haven't run them at scale. Also, "self-healing" isn't really one thing. There are hundreds of different problems that can take out such a cluster, and every single one of them needs its own "self-healing" mechanism. These systems are literally the most complicated kinds of systems.

"Should have self healing" can be expanded into "should have systems to address the underlying system failure modes", which starts to shed some light into why distributed systems will always run into failure modes.

Re: Fly.io Status – Consul cluster outage

#122
post #116

Earlier quoted context omitted.

Out of interest why would one presume that they are being actively supported? I haven’t read everything about this saga, but I’ve never seen any mention of a commercial relationship.

If you're on a slowly-sinking ship, it'd be silly not to at least try to bring in someone with the full context of the ship's architecture to get it serviceable before going all-in on the decision to engineer and build an entirely new kind of ship while still aboard the sinking one.

That’s not really what I asked: do you have any actual evidence of a commercial relationship rather than the notion that it wouldn’t be a bad idea?

Re: Fly.io Status – Consul cluster outage

#123
post #98

Earlier quoted context omitted.

To add a data point we've been using Consul globally for several years now without any major outages. We do close to 50k qps with Consul at peak running on single digit cores per DC.

50k qps on consul or system wide?

Consul specifically
Post reply on HN