Course contentsShow
← Cloud and Infrastructure
Lesson 1802 of 2,98937. JenkinsFree lesson

Jenkins High Availability Architecture

Design fault-tolerant Jenkins setups with primary-replica patterns and shared storage for controller HA.

Jenkins High Availability Architecture

What You'll Learn

You'll learn how to design fault-tolerant Jenkins setups using primary-replica patterns and shared storage to keep your CI/CD pipeline running even when failures occur.

Why High Availability Matters

When Jenkins goes down, your entire CI/CD pipeline stops—no builds, no deployments, no tests. For production systems, this is unacceptable. High Availability (HA) ensures Jenkins remains operational even during hardware failures, maintenance, or unexpected crashes.

Core HA Architecture Pattern

The primary-replica pattern (also called active-passive or master-standby) is the foundation of Jenkins HA:

  • Primary controller: Handles all active requests and orchestrates builds
  • Replica controller(s): Standby instance(s) ready to take over if the primary fails
  • Shared storage: Both controllers access the same JENKINS_HOME directory containing jobs, configurations, and build history

Think of it like having two pilots in an airplane cockpit—only one flies at a time, but both have access to the same instruments and can take control instantly if needed.

Key Components for HA

Shared Storage: Use network-attached storage (NFS, EFS, GlusterFS) or cloud block storage to ensure both controllers can read/write the same Jenkins data. Without this, your replica won't have up-to-date job configurations.

Load Balancer: Routes traffic to the active controller and performs health checks. When the primary fails, it redirects to the replica.

State Synchronization: The replica must monitor the primary's health and coordinate takeover to prevent split-brain scenarios (both thinking they're primary).

Limitations and Considerations

  • Brief downtime occurs during failover (~30-60 seconds)
  • Agents reconnect automatically after controller switch
  • Running builds may need to restart
  • Shared storage becomes a single point of failure—choose a resilient solution

Key Takeaway: Jenkins HA uses primary-replica controllers with shared storage and load balancing to minimize downtime, ensuring your CI/CD pipeline stays operational during failures.