Responding to Ghost
Jan 28, 2015Jacob Vosmaer
Summary
This post details the process of applying OS-level security patches (glibc vulnerability) to production systems with minimal downtime by leveraging the existing DRBD-based clustered setup for fast failovers. It outlines the steps of updating OS packages and rebooting servers, and specifically highlights how the DRBD-based clustered setup enabled a failover in under a minute to apply updates to the standby server, minimizing downtime for gitlab.com.
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