3 ms·
That wouldn't have really helped them here though? If the closely connected storage nodes were unable to detect whether state was consistent, how would have the
by robryan 14y ago
That wouldn't have really helped them here though?
If the closely connected storage nodes were unable to detect whether state was consistent, how would have the storage node in another data center known?
I guess what your saying is in an error making the site entirely read only from another data center. That could be of some use but I would imagine that would require a complete rearchitecture to separate out all writes and also have a method of recombining stuff like logging which will still be written later on.
On the git level though it would be useful for a major use case of github which is to grab code.
- chuhnk 14y agoIf its a fileserver pair that go down and they are serving a subset of repos then what do you do? Well you could keep serving all the other repos and start a recovery process, whatever that may be. Perhaps redirect the requests for those repos to another datacenter where there's another copy. Or make the decision of failing over the entire site from primary to secondary datacenter. My point was really from the standpoint of a system and network wide outage for which it will take multiple hours to recover. Its about business continuity. I've been making comments from the standpoint of a user and the open source community but what about from the other side. I guess its a subscription like service for paid for customers so it has no immediate consequence on revenue but in places I've worked downtime is money lost and customers would actually require us to have SLAs and disaster recovery procedures in place before they would sign contracts with us. Anyway, yea the step from single server to multi server, to multiple datacenters does normally involve some re-architecting at the state layer, everything else is load balancing.