Re:Fly.io Postgres cluster down for 3 days, no word from the...
by marcinzm on Friday July 21, 2023 @06:08AM
(#36812045)
Downtime but limited downtime since the data is stored with triple redundancy across multiple machines in the same AZ. So unless the AZ goes down (which is a different failure than what happened here) you can restart the DB on a different instance pretty quickly and I'm guessing AWS will do it automatically for you.
Re:Fly.io Postgres cluster down for 3 days, no word from the...
by truetraveller on Friday July 21, 2023 @07:27AM
(#36812543)
I don't believe their RDS / EBS has 3x redundancy. With SSD, that would be super costly for them. But if that's correct, that would be incredible.
Re:Fly.io Postgres cluster down for 3 days, no word from the...
by marcinzm on Friday July 21, 2023 @07:48AM
(#36812731)
May not be 3x but it is replicated so even a total instance failure would not make you lose data:
>Amazon EBS volumes are designed to be highly available, reliable, and durable. At no additional charge to you, Amazon EBS volume data is replicated across multiple servers in an Availability Zone to prevent the loss of data from the failure of any single component. For more details, see the Amazon EBS Service Level Agreement.
https://aws.amazon.com/ebs/features/#Amazon_EBS_availability...
Re:Fly.io Postgres cluster down for 3 days, no word from the...
by williamdclt on Friday July 21, 2023 @07:48AM
(#36812724)
> Maybe not with Aurora
If a read replica fails, I'd expect no downtime (possibly a few errors as connections get cut off abruptly). Although there's always the risk that the remaining instances aren't able to handle the additional load.
If the master fails, you'll get a ~2min downtime
And +1 to the sibling comment; Fly makes it very clear that single instance postgres isn't HA, and talks about what you need to do architecturally to maintain uptime.