ドキュメントには頻繁に更新が加えられ、その都度公開されています。本ページの翻訳はまだ未完成な部分があることをご了承ください。最新の情報については、英語のドキュメンテーションをご参照ください。本ページの翻訳に問題がある場合はこちらまでご連絡ください。
記事のバージョン: Enterprise Server 2.21

About clustering

GitHub Enterprise Server clustering allows services that make up GitHub Enterprise Server to be scaled out across multiple nodes.

ここには以下の内容があります:

Clustering architecture

GitHub Enterprise Server is comprised of a set of services. In a cluster, these services run across multiple nodes and requests are load balanced between them. Changes are automatically stored with redundant copies on separate nodes. Most of the services are equal peers with other instances of the same service. The exceptions to this are the mysql-server and redis-server services. These operate with a single primary node with one or more replica nodes.

Learn more about services required for clustering.

Is clustering right for my organization?

クラスタリングは、負荷を複数のノードに分配することによってスケーラビリティを向上させます。 この水平スケーリングは、数万の開発者を持つような組織に適しているかもしれません。 However, setting up a redundant and scalable cluster can be complex and requires careful planning. This additional complexity will need to be planned for during installation, disaster recovery scenarios, and upgrades.

GitHub Enterprise Server requires low latency between nodes and is not intended for redundancy across geographic locations.

Clustering provides redundancy, but it is not intended to replace a High Availability configuration. For more information, see High Availability configuration. A primary/secondary failover configuration is far simpler than clustering and will serve the needs of many organizations. For more information, see Differences between Clustering and High Availability.

How do I get access to clustering?

Clustering is designed for specific scaling situations and is not intended for every organization. If clustering is something you'd like to consider, please contact your dedicated representative or GitHubの営業チーム.

担当者にお尋ねください

探しているものが見つからなかったでしょうか?

弊社にお問い合わせください