...
The
D s platform | ||
---|---|---|
|
Info | |
---|---|
NOTE: This section applies to deployments of the
|
The
D s platform |
---|
...
- communicates with the same database
- shares the
/opt/trifacta/conf
and/opt/trifacta/logs
directories through NFS.
- Database: PostGreSQL supports HA. The HA-enabled database runs outside of the cluster of platform nodes and appears to each node as a single database. No application code changes are required.
- Load balancer: HAProxy is used for its capabilities on health checking the other HA nodes. This load balance periodically checks the health of the other nodes in the setup.
- If the health for a given node fails, then the load balancer stops routing traffic to that node while continuing to poll its health.
- If the node recovers, the load balancer resumes sending traffic to it.
- Node health is described below.
- Synchronized configuration: All nodes share the
/opt/trifacta/conf
mount point, which allows the same configuration files to be visible and accessible on each node.
...
All nodes must meet the system requirements. See System Requirements in the Planning Guide.
All nodes must have the appropriate ports opened. See System Ports in the Planning Guide.
Install the databases.
Info NOTE: The databases must be installed in a location that is accessible to all nodes.
Info NOTE: When installing databases for high availability access, you should deploy standard access and replication techniques that are consistent with the policies of your enterprise.
See Install Databases in the Databases Guide.
Complete the installation process for the server node.
Info NOTE: After install, do not start the
.D s node See Install Software.
Repeat the above process for each of the client nodes.
- The software is installed on all nodes. No node is running the software.
...