GitLab.com outage on 2015-05-29
Jun 4, 2015Jacob Vosmaer

Summary
This post details a specific outage on GitLab.com due to an infrastructure upgrade that moved to a clustered setup. The root cause was identified as a backup script hanging during the filesystem freeze/unfreeze process on the backend server, which prevented workers from mounting the NFS share. The extended downtime was attributed to insufficient training and documentation for on-call engineers regarding the new infrastructure. Next steps included removing the filesystem freeze from the backup script, implementing a secondary backup strategy for SQL data, and initiating regular operations drills for on-call engineers.
More from the High Availability trail
- Consolidate your GitLab stack with Gitaly on Kubernetes
- GitLab backs 99.9% availability SLA with service credits
- Downtime happens, but GitLab Incident Management can help
- How we are closing the gap on replicating *everything* in GitLab Geo
- How we tested a feature that affected (almost) all parts of GitLab