3 ms·
> they should take a hard look at their application and see if they can architect it in a way that does not require a complex distributed filesystem to present
by daxelrod 10y ago
> they should take a hard look at their application and see if they can architect it in a way that does not require a complex distributed filesystem to present a single mount that they can expose over NFS
As someone who administers GitLab for my company, yes please.
Any high availability scenario that involves "just mount the same NFS volume on your standby" is a nonstarter for us. (We've found mounting NFS across different datacenters to be too unreliable and our failover scenarios include loss of a data center.)
It would also be wonderful to be able to run GitLab in any of the PaaSes that only have ephemeral disk, but that's a secondary concern.
- closeparen 10y ago>Any high availability scenario that involves "just mount the same NFS volume on your standby" is a nonstarter for us What are the alternatives? I suppose there's MySQL's "stream asynchronously to the standby at the application level." ... which, now that I think about it, should be pretty easy to do with Git, since pushing and pulling discrete units of data are core concepts...
- daxelrod 10y agoYep! See GitHub's Spokes, née DGit. http://githubengineering.com/building-resilience-in-spokes/ http://githubengineering.com/building-resilience-in-spokes/