分布式和高可用性安装
- 版本 ：2022.1 及更高版本
运行 Tableau Server 的最基本方法是安装单个节点。通过这种类型的安装，您将拥有一个功能齐全的 Tableau Server，其中所有 Tableau Services Manager （TSM） 和 Tableau Server 进程都在该单个节点上运行，但这可能不是使用 Tableau Server 的最佳方式。
您可以根据组织的需求和资源来决定如何安装 Tableau，添加其他节点并配置 Tableau 以实现高可用性。您的安装选项包括：
单节点安装 — 这种类型的安装对于测试、运行试验以及可能因缺少冗余而可以处理偶尔停机和系统可用性的环境是合理的。所有服务器进程都在一台计算机上运行。在其中一个服务器进程出现问题时，冗余更少，保护措施更少。您还需要确保安装 Tableau Server 的计算机具有足够的资源来处理流程以及用户和数据的需求。
分布式安装 - 这种类型的安装也称为多节点安装，需要多台计算机，以便您可以在这些分布式节点上安装和运行服务器进程。将服务器进程分散到多个节点上，可以通过提供冗余和额外的计算能力来扩展 Tableau Server 的可靠性和效率。通过正确的配置，分布式安装还可以为您提供自动存储库故障转移。有关故障转移的详细信息，请参 阅存储库故障转移 。
高可用性 （HA） 安装 - Tableau Server 的 HA 安装是一种特殊类型的多节点安装，在不同的计算机上至少有三个节点和多个关键进程实例（存储库、文件存储/数据引擎 （Hyper）、协调服务和客户端文件服务）。通过 HA 安装，这些关键进程具有内置的冗余，包括多个文件存储和自动存储库故障转移。目标是通过消除单点故障，并在可能的情况下通过故障转移来检测故障，从而最大限度地减少系统停机时间。
在初始节点发生故障或运行应用程序服务器 （VizPortal） 的节点正在从故障中恢复时，仍可能出现停机。仪表板和视图的加载速度可能比预期的要慢，并且可能会出现超时，具体取决于系统的配置和使用方式。有关初始节点故障的详细信息，请参阅下面的初始节点发生故障时。
安装 Tableau 的第一台计算机（即“初始节点”）具有一些独特的特征。三个进程仅在初始节点上运行，不能移动到任何其他节点，除非在故障情况下，许可证服务（许可证管理器）、激活服务和 TSM 控制器（管理控制器）。Tableau Server 包含一个脚本，该脚本可自动将这些进程移动到其他现有节点之一，以便您可以完全访问 TSM 并保持 Tableau Server 运行。
另外两个进程最初包含在初始节点上，但可以添加或移动到其他节点，即 CFS（客户端文件服务）和协调服务。根据使用 CFS 和协调服务配置安装的方式，您可能还需要采取措施重新部署这些内容。
有关将许可证服务和 TSM 控制器从初始节点移动到另一个节点的信息，请参阅下面的从初始节点故障中恢复。
先决条件
这些说明假定您的集群满足分布式要求。
注意：多节点群集中的所有节点必须具有相同类型的操作系统。您不能在 Linux 和 Windows 节点的组合上安装 Tableau Server 的多节点实例。
发 牌
您必须具有有效的 Tableau Server 产品密钥。您拥有的许可证类型可能决定了您可以在多少个节点上安装 Tableau。您不能将试用许可证密钥用于分布式 Tableau Server 安装。有关许可的详细信息，请参阅许可概述。
创建分布式 Tableau Server 安装
以下是创建 Tableau Server 分布式安装时要遵循的一般步骤：
首先在初始节点上安装 Tableau Server。
有关详细信息，请参阅安装和配置 Tableau 服务器。
在初始节点上生成节点配置（引导程序）文件。
有关详细信息，请参阅生成节点引导程序文件。
使用节点引导程序文件在其他节点上安装 Tableau Server。
使用要在其上运行的进程配置其他节点。
对要安装的任何其他节点重复步骤 3 和 4。
部署新的协调服务整体。
有关详细信息，请参 阅部署协调服务整体 。
将客户端文件服务添加到运行协调服务的每个节点。
有关详细信息，请参 阅配置客户端文件服务 。
创建高可用性 （HA） Tableau Server 安装
高可用性 Tableau Server 安装是一种特殊类型的分布式安装，旨在适应关键服务器组件中的故障，而不会丢失完整的服务器功能。要创建 HA 安装，请按照创建分布式部署时执行的相同步骤操作，但包括使部署高度可用的其他步骤。这些附加步骤包括添加至少两个附加节点（群集中至少三个节点）、添加存储库的第二个实例和数据引擎/文件存储的第二个实例、添加其他网关进程以及部署协调服务整体。您还可以添加负载均衡器以在网关之间分发请求。
从高层次上讲，以下是创建 Tableau Server 高可用性安装时所遵循的步骤：
首先在初始节点上安装 Tableau Server。
有关详细信息，请参阅安装和配置 Tableau 服务器。
在初始节点上生成节点配置（引导程序）文件。
For details, see Generate the node bootstrap file.
Install Tableau Server on at least two additional nodes using the node bootstrap file.
For more information, see Install and initialize an additional node.
Configure each additional node with the processes you want to run on it. These must include a second copy of the Tableau Server repository, and a second copy of the data engine and file store, as well as additional instances of the gateway.
For more information, see Configure the additional node.
Deploy a Coordination Service ensemble.
For more information, see Deploy a Coordination Service Ensemble .
Add Client File Service to every node that is running the Coordination Service.
For more information, see Configure Client File Service .
(Optional) Configure a load balancer.
For more information, see Add a Load Balancer.
For details on how to create a three-node HA installation, see Example: Install and Configure a Three-Node HA Cluster.
If an initial node fails
If there is a problem with the initial node and you have redundant processes on your other nodes, there is no guarantee that Tableau Server will continue to run. Tableau Server can continue to run for up to 72 hours after an initial node failure, before the lack of the licensing service impacts other processes. If so, your users may be able to continue to sign in and see and use their content after the initial node fails, but you will not be able to reconfigure Tableau Server because you won't have access to the Administration Controller.
Even when configured with redundant processes, it is possible that Tableau Server may not continue to function after the initial node fails. This is true even when an installation is configured for high availability. This means you should make a point of moving the two unique processes to another of your running nodes as soon as possible. If your initial node fails for reasons that are recoverable in a relatively short amount of time (for example, a hardware failure you can correct), you should first attempt to bring the node back up without using the procedure below.
Recover from an initial node failure
With a Tableau Server installation, the initial node includes two services that are only installed on that node, the License service, and the TSM Controller. If there is a problem with the initial node, Tableau Server may not continue to function, even when configured for high availability. To recover from a situation where the initial node fails, you can move the TSM Controller and the License service to one of your already configured nodes. This allows you to recover from the failure while using resources you already have in the cluster. You do not have to configure a standby initial node in case the initial node fails.
For details on how to recover from a failure on the initial node, see Recover from an Initial Node Failure.
Configure Coordination Service ensemble on additional nodes
Configuring a Coordination Service on multiple nodes provides additional duplication of processes and so reduces the possibility of server downtime due to an issue with one of the Coordination Service nodes. For details on how to deploy a Coordination Service ensemble on your cluster, see Deploy a Coordination Service Ensemble .
Add Client File Service (CFS) to additional nodes
Tableau Server requires at least one instance of Client File Service (CFS). Adding additional instances of CFS to other nodes provides additional duplication of processes and so reduces the possibility of server downtime due to an issue with one of the CFS nodes. We recommend that you configure an instance of CFS on each of the nodes where you deploy the Coordination Service. For details on how to configure CFS on other nodes, see Configure Client File Service .
Tableau Server service license check
A number of processes are installed when you install Tableau Server. Some of these processes are dependent on the existence of a valid Tableau Server license while other installed processes are not. The subset of Tableau Server that require a valid Tableau Server license are considered "licensed processes."
When a licensed process starts or restarts, the process checks with the Tableau Server License Manager service on the primary node to verify there is a valid license. When the License Manager validates the license, the process is fully functional and able to respond to requests from other Tableau Server processes. Once a licensed process has received confirmation from the License Manager, the process does not need to reconfirm the license for 72 hours, or until the process restarts. If the process is not able to verify that it is licensed (if the primary node is unavailable, for example) it cannot run, but it continues to check for a valid license until it confirms the license. To see when the last licensing check occurred, look at the log files in the ProgramData\Tableau\Tableau Server\data\tabsvc\logs\licenseservice folder. For more information about licensed processes, see Licensed processes.