3 ms·
When I hear "It's one of those things that talks to other instances of itself" I think of a redundant, high-availability database. Assuming every machine sends
by michaelt 7y ago
When I hear "It's one of those things that talks to other instances of itself" I think of a redundant, high-availability database.
Assuming every machine sends data to all its peers regularly, if I have a cluster of 10 A machines and upgrade 1 machine to B, and the A machines crash, that means I lose 90% of my capacity - likely making the sole survivor get overwhelmed too.
"Outages are OK, clients can always reconnect or try again later" isn't the usual standard HA databases are operated to :D
- Aeolun 7y agoAt that point the A machines are dead though. There is no point in restarting them as A when you can also restart them as B, so I assume they don’t all die in one go. But I guess we just have too little information to make a really informed decision about what you should do.
- klodolph 7y ago> There is no point in restarting them as A when you can also restart them as B, so I assume they don’t all die in one go. A is “baked in”, so it should be the default. There are simply too many classes of bugs which take time to manifest. Memory leaks, cache staleness, etc. So, for very good reasons, you consider version A preferable to version B.
- narag 7y agoWhen I hear "It's one of those things that talks to other instances of itself" I think of a redundant, high-availability database. Oh, I thought of an ancient copy of Windows for Workgroups taking down the Windows NT 4 domain servers every single day. Real story. But that case was version A crashing version B, not the other way around.