Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version next


  • This form of high availability is not supported for Marketplace installations.
  • Job canceling does not work.
  • When HA is enabled, the restart feature in the Admin Settings page does not work. You must restart using the command line.
  • The platform must be installed on /opt/trifacta on every failover node.
  • This feature does not apply to the following components:
    • Hadoop cluster (See previous link.)
    • webhdfs/httpfs
    • Hive
    • Sentry
    • Navigator
    • Atlas
    • any other application/infrastructure with which the 
      D s platform
       can integrate


  • Database: PostGreSQL supports HA. The HA-enabled database runs outside of the cluster of 
    D s item
     and 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. 


  1. All nodes must meet the system requirements. See System Requirements.

  2. All nodes must have the appropriate ports opened. See System Ports.

  3. Install the databases.


    NOTE: The databases must be installed in a location that is accessible to all nodes.


    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.

  4. Complete the installation process for the server node.


    NOTE: After install, do not start the


    See Install Software.

  5. Repeat the above process for each of the client nodes.

  6. The software is installed on all nodes. No node is running the software.