3.2 Deployment Options

You can choose to deploy in a single-node or multi-node environment, depending on your anticipated workload and whether you need high availability. For more information about deployment sizing and tuning, see Hardware Requirements and Tuning Guidelines.

If you already have an existing cluster for Transformation Hub or ArcSight Investigate, you can deploy Identity Intelligence to the same cluster. Reusing existing clusters would reduce costs and system management effort compared to deploying these software in a new cluster.

3.2.1 Single-node Deployment

In a single-node deployment, you deploy all of the Identity Intelligence components on a single node. This method of deployment is suitable only for small workloads and where you do not need high availability.

3.2.2 Multi-node Deployment

For larger workloads, you must deploy Identity Intelligence and the required software in a multi-node cluster setup. Multi-node deployment does load balancing across several worker nodes and is scalable to handle large workloads. You can add multiple master nodes and worker nodes to scale. While you can add worker nodes even after the installation, you can add master nodes only during the installation. Therefore, plan your deployment before you start the installation process.

3.2.3 High Availability Deployment

To avoid single point failures and reduce downtime, you should ensure that your deployment is highly available.

For high availability deployment, you must set up three master nodes and at least two or more worker nodes depending on the workload. For information about the number of worker nodes for different workloads, see System Requirements. Three master nodes are required to ensure that even in cases where two master nodes are unavailable, there is still another master node available. If only two master nodes are used and the primary master node is taken offline for maintenance or upgrade, there will only be a single master node available creating a single point of failure. If the available single master node fails, the cluster stops and cluster orchestration will not be possible until the master is back online.

For high availability of Vertica, you must set up three Vertica nodes.

While you can add worker nodes even after the installation, you can add master nodes only during the installation. Therefore, plan your deployment before you start the installation process.