可用性计算_高可用性计算简介：概念和理论

可用性计算

Let’s focus more on some of the larger architectural principles of cluster management than on any single technology solution.

让我们更多地关注集群管理的一些更大的体系结构原理，而不是任何单一技术解决方案。

We get to see some actual implementations later in the book - and you can learn a lot about how this works on Amazon’s AWS in my Learn Amazon Web Services in a Month of Lunches book from Manning. But for now, let’s first make sure we’re comfortable with the basics.

在本书的后面，我们将看到一些实际的实现-您可以在《 Manning 的一个月的午餐学习亚马逊 》一书中，学到很多关于它如何在Amazon AWS上工作的信息 。 但是现在，让我们首先确保我们对基础知识感到满意。

Running server operations using clusters of either physical or virtual computers is all about improving both reliability and performance over and above what you could expect from a single, high-powered server. You add reliability by avoiding hanging your entire infrastructure on a single point of failure (i.e., a single server). And you can increase performance through the ability to very quickly add computing power and capacity by scaling up and out.

使用物理或虚拟计算机的群集运行服务器操作的全部目的在于提高可靠性和性能，这超出了单台高性能服务器的预期。 通过避免将整个基础架构挂在单个故障点(即单个服务器)上来增加可靠性。 您还可以通过向上和向外扩展来快速增加计算能力和容量，从而提高性能。

This might happen through intelligently spreading your workloads among diverse geographic and demand environments (load balancing), providingbackup servers that can be quickly brought into service in the event a working node fails (failover), optimizing the way your data tier is deployed, or allowing for fault tolerance through loosely coupled architectures.

这可能是通过在不同的地理环境和需求环境中智能地分散工作负载(负载平衡)，提供可以在工作节点发生故障(故障转移)时快速启用的备份服务器，优化数据层的部署方式或允许通过松散耦合的体系结构实现容错。

We’ll get to all that. First, though, here are some basic definitions:

我们将处理所有这些。 首先，这里有一些基本定义：

Node: A single machine (either physical or virtual) running server operations independently on its own operating system. Since any single node can fail, meeting availability goals requires that multiple nodes operate as part of a cluster.

节点 ：单台计算机(物理或虚拟)在其自己的操作系统上独立运行服务器操作。 由于任何单个节点都可能发生故障，因此要达到可用性目标，就需要多个节点作为集群的一部分进行操作。

Cluster: Two or more server nodes running in coordination with each other to complete individual tasks as part of a larger service, where mutual awareness allows one or more nodes to compensate for the loss of another.

群集 ：两个或多个服务器节点相互协作运行，以完成一项较大的服务中的单个任务，而相互了解可以使一个或多个节点补偿另一个节点的损失。

Server failure: The inability of a server node to respond adequately to client requests. This could be due to a complete crash, connectivity problems, or because it has been overwhelmed by high demand.

服务器故障 ：服务器节点无法充分响应客户端请求。 这可能是由于完全崩溃，连接问题，或者是由于需求过大而导致的。

Failover: The way a cluster tries to accommodate the needs of clients orphaned by the failure of a single server node by launching or redirecting other nodes to fill a service gap.

故障转移 ：集群通过启动或重定向其他节点来填补服务缺口，从而尝试满足因单个服务器节点故障而孤立的客户端需求的方式。

Failback: The restoration of responsibilities to a server node as it recovers from a failure.

故障回复 ：服务器节点从故障中恢复时责任的恢复。

Replication: The creation of copies of critical data stores to permit reliable synchronous access from multiple server nodes or clients and to ensure they will survive disasters. Replication is also