Article version: Enterprise Server 2.15

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2019-10-16. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Managing a GitHub Enterprise Server cluster

Plan maintenance operations for a GitHub Enterprise Server cluster, such as upgrades, adding capacity, and replacing failed nodes.

Upgrading a cluster

Use the administrative shell (SSH) to upgrade a GitHub Enterprise Server cluster to the latest release.

Replacing a cluster node

To replace a GitHub Enterprise Server node, you must mark the affected nodes offline in the cluster configuration file (cluster.conf) and add the replacement nodes. This might be necessary if a node were to fail, or to add a node with more resources to increase performance.

Evacuating a cluster node

You can evacuate data services on a cluster node.

Monitoring cluster nodes

A GitHub Enterprise Server cluster is comprised of redundant services that are distributed across two or more nodes. If an individual service or an entire node were to fail, it should not be immediately apparent to users of the cluster. However since performance and redundancy are affected, it is important to monitor the health of a GitHub Enterprise Server cluster.

Ask a human

Can't find what you're looking for?

Contact us