4 ms·

So, maybe a stupid question from a frontend dev who doesn't deal with these systems at all, but aren't these systems usually part of a cluster with read replica

So, maybe a stupid question from a frontend dev who doesn't deal with these systems at all, but aren't these systems usually part of a cluster with read replicas? Blowing away the contents of one box shouldn't destroy the cluster right? I thought the primary/secondary pattern was really common among relational databases and failover boxes and other measures were standard practice. Was the command executed on all machines? Is the cluster treated as one file system? Please excuse the ignorance.

yeukhon 10y ago
You'd be surprised how many companies out there do not run read replica and don't really have anything for disaster recovery (same data center, same country good luck when there's an outage).
terom 10y ago
Replication systems can break. They work working on fixing the broken db2 read replica when they accidentially nuked the primary db1 server. > db2.cluster refuses to replicate, /var/opt/gitlab/postgresql/data is wiped to ensure a clean replication > [...] decides to remove the directory. After a second or two he notices he ran it on db1.cluster.gitlab.com, instead of db2.cluster.gitlab.com That ops fail on db1 wouldn't have been such an issue if they weren't in such a vulnerable position with an invalidated read replica.