When your writer node is suffixed with "-ro"
By - parens-r-us
Some people like to watch the world burn
Actually, in Bajoran it's traditional for the "Ro" to go first.
Whenever people talk about enterprise code, I wonder how their bad coding practices relate NCC1701
rite only 😂
I don't get it.
no it means "read-out" as in you should read out loud the binary to a speech to text processor to run it
i think it means "red olive" or maybe that was just a very small tomato
It's "red oil", the kind of lubricant you're supposed to use when performing maintenance to the DB.
Underlibricated database spindles is a major cause of internet outage to this day.
The machine spirits must be appeased
i think it means "red olive". that or it was a very small tomato
The entire point of having multiple database instances with replication is so that if your writer node fails one of the other instances can take over with no downtime. They can also fail-over during maintenance or upgrades.
You never want to include read-only in the instance name, because you don't have any control over when failovers happen as they are usually automatic.
The replicas have to replicate all the same writes that the main database does, so what load are you saving?
And again, the writer instance can and should change over time.
He's not "just wrong". You're both right (depending on the technology). Failover is a different need from read availability. A transactionally consistent slave provides both functions of providing availability and fault tolerance. Though you'd really want three. Idea if you're expecting to support the same level of availability during a failover.
Check event history they might have failed over at some point
Is that how AWS DB clusters work? (Genuine question)
Yes they switch all the time. I think usually when updates require a restart or something. It’s annoying because if you have to use the IP, that also changes.
Wth, then why would you call them using a "-ro" suffix, wouldn't it make more sense to just call them -1 and -2? (or maybe letters, or colors as in blue-green deployment)
Yeah that's what we do now. 1,2,3,4
When I was first messing around with them, I named them "primary" and "backup" or something. After I understood how the failover worked, I changed them to 1,2
You wouldn't. The real horror here is the instance naming, not that the writer changed.
Could be Romanian
Someone had to scale up or fail over I'm guessing. Bad naming convention though.
Worse yet if that's the developers initials.
RO stands for "rectal orifice" because the writer just dumps shit into the database.
Yeah it’s rite only. What part of that is so difficult to understand? /s
It actually probably started out as a replica and then failed over to become the writer
This is because AWS will awitch the reader and writer nodes whenever maintenance is done on the cluster. So naming one node as a reader or writer won't be accurate for long.