In a GitHub Enterprise Server cluster configuration, what is the role of a 'primary' datacenter?
Select an answer to reveal the explanation.
Short Explanation and Infographic
In GHES multi-datacenter clustering, the primary datacenter is where writes land. Secondary datacenters serve reads for users near them, dramatically reducing latency. When the primary goes down, a secondary can be promoted.
Full explanation below image
Full Explanation
GitHub Enterprise Server clustering with multiple datacenters uses a primary-secondary model for write operations. The primary datacenter handles all write operations (new commits, issue creation, PR updates) while secondary datacenters serve read traffic and provide local caching for users in their geographic region. This architecture: (1) Reduces latency for geographically distributed teams by serving reads locally. (2) Maintains write consistency through a single primary. (3) Provides failover capability if the primary datacenter becomes unavailable. Configuration requires careful network topology planning including low-latency connections between datacenters for replication. This is distinct from the simpler HA configuration (two nodes, one active/one passive) — clustering supports active read serving from multiple sites.