我们经常发布文档更新,此页面的翻译可能仍在进行中。有关最新信息,请访问英文文档。如果此页面上的翻译有问题,请告诉我们
文章版本: Enterprise Server 2.21

Differences between clustering and high availability (HA)

GitHub Enterprise Server High Availability Configuration (HA) is a primary/secondary failover configuration that provides redundancy while Clustering provides redundancy and scalability by distributing read and write load across multiple nodes.

本文内容

Failure scenarios

High Availability (HA) and Clustering both provide redundancy by eliminating the single node as a point of failure. They are able to provide availability in these scenarios:

  • 软件崩溃,操作系统失败或不可恢复的应用程序所致。
  • 硬件故障,包括存储硬件、CPU、RAM、网络接口等。
  • 虚拟化主机系统故障,包括 AWS 上未计划和计划内的维护事件
  • 逻辑或物理服务网络(如果故障转移设备在不受故障影响的单独网络上)。

Scalability

集群通过跨多个节点分配负载而提供更好的可扩展性。 这种横向扩展能力可能更适合某些拥有数万名开发者的组织。 In HA, the scale of the appliance is dependent exclusively on the primary node and the load is not distributed to the replica server.

Differences in failover method and configuration

FeatureFailover configurationFailover method
High Availability ConfigurationDNS record with a low TTL pointed to the primary appliance, or load balancer.You must manually promote the replica appliance in both DNS failover and load balancer configurations.
ClusteringDNS record must point to a load balancer.If a node behind the load balancer fails, traffic is automatically sent to the other functioning nodes.

Backups and disaster recovery

Neither HA or Clustering should be considered a replacement for regular backups. For more information, see "Configuring backups on your appliance."

Monitoring

Availability features, especially ones with automatic failover such as Clustering, can mask a failure since service is usually not disrupted when something fails. Whether you are using HA or Clustering, monitoring the health of each instance is important so that you are aware when a failure occurs. For more information on monitoring, see "Recommended alert thresholds" and "Monitoring cluster nodes."

Further reading

问问别人

找不到要找的内容?

联系我们