Deployment Types

The Fusion platform is designed to support enterprise search applications at any scale. You can deploy Fusion across multiple nodes in order to store large amounts of data or to achieve high processing throughput or both.

Fusion consists of a number of Java processes that run in JVMs, including the api, connectors, and ui processes, and possibly others such as spark-master and spark-worker. When you start Fusion, the processes that start are listed. You might also see zookeeper and solr processes, depending on the cluster arrangement. An external SolrCloud cluster can have its own ZooKeeper clusters. For more information, see link:[Components].

Deployment goals

  • Demo, trial, and development deployments – The simplest possible architecture is the one you get out of the box, by unpacking the tar/zip file and running fusion/3.1.x/bin/fusion start, so that all components (including the bundled Solr and ZooKeeper instances) run on a single host in their default configurations.

    You can quickly install and run Fusion on a computer (even on your laptop) to explore its features and work with sample data. See Getting Started for Quickstart instructions. This diagram illustrates a single-node Fusion deployment:

    Fusion on a single node

  • Onsite late-stage development and test deployments – Ideally, an onsite deployment for late-stage development and testing should have the same architecture as the production deployment, though it doesn’t need to be scaled to provide the same level of service.

  • Production deployments – Fusion is designed for flexible, distributed deployment. Any of its components can be distributed across your network, and some can be clustered. A production deployment requires multiple Fusion nodes, each of which runs some or all Fusion services. Solr might run on the same nodes or run in an external SolrCloud cluster. ZooKeeper should run on separate nodes. An external SolrCloud cluster might have its own ZooKeeper nodes.

Cluster Arrangements

You can deploy Fusion across multiple nodes in a Fusion cluster and use a ZooKeeper cluster as the centralized, synchronized store for both application configurations and user data. For production deployments, the ZooKeeper cluster is usually external to the Fusion cluster. For test deployments, you can use the bundled ZooKeeper on the Fusion nodes.

Regarding Solr, you can use the bundled Solr on Fusion nodes, except for very large deployments, for which you should use an external SolrCloud cluster. If you already have SolrCloud clusters managing your data, you can integrate them into a Fusion deployment.

To satisfy processing requirements, install Fusion, ZooKeeper, and Solr on specific nodes. These are the possibilities:

ZooKeeper cluster on separate nodes

In these Fusion cluster arrangements, the ZooKeeper cluster is on separate (non-Fusion) nodes.

  • Cluster arrangement 1: ZooKeeper cluster on separate nodes & same-node Solr instances – Each node in the Fusion cluster has Fusion and Solr installed.

    Same-node Solr instances

Here are installation instructions for Unix and Windows.

  • Cluster arrangement 2A: External and separate SolrCloud and ZooKeeper clusters – Each node in the Fusion cluster has Fusion installed. Fusion uses an external SolrCloud cluster for both data (for example, signals, aggregated signals, and indexes) and logs. The ZooKeeper cluster is on non-Fusion, non-Solrcloud nodes.

    External and separate SolrCloud and ZooKeeper clusters

Here are installation instructions for Unix and Windows.

  • Cluster arrangement 2B: External SolrCloud cluster with ZooKeeper cluster on SolrCloud nodes – Each node in the Fusion cluster has Fusion installed. Fusion uses an external SolrCloud cluster for both data (for example, signals, aggregated signals, and indexes) and logs. The ZooKeeper cluster is on the SolrCloud nodes.

    External SolrCloud cluster

Here are installation instructions for Unix and Windows.

  • Cluster arrangement 3A: ZooKeeper cluster on separate nodes & both same-node Solr instances and an external SolrCloud cluster – Each node in the Fusion cluster has Fusion and Solr installed, and there is a SolrCloud cluster on other nodes. Fusion uses the same-node Solr instances for logs and for raw signal data. Fusion uses the external Solr instances for aggregated signal data and indexes. The ZooKeeper cluster is on non-Fusion, non-Solrcloud nodes.

    Same-node Solr plus SolrCloud

Here are installation instructions for Unix and Windows.

  • Cluster arrangement 3B: ZooKeeper cluster on separate nodes & both same-node Solr instances and an external SolrCloud cluster – Each node in the Fusion cluster has Fusion and Solr installed, and there is a SolrCloud cluster on other nodes. Fusion uses the same-node Solr instances for logs and for raw signal data. Fusion uses the external Solr instances for aggregated signal data and indexes. The ZooKeeper cluster is on the SolrCloud nodes.

    Same-node Solr plus SolrCloud

Here are installation instructions for Unix and Windows.

ZooKeeper cluster on Fusion nodes

In these Fusion cluster arrangements, the ZooKeeper cluster is on Fusion nodes.

Note
We don’t recommend these cluster arrangements for production Fusion clusters. Place ZooKeeper on separate nodes.
  • Cluster arrangement 4: ZooKeeper cluster on Fusion nodes & same-node Solr instances – Each node in the Fusion cluster has Fusion, Solr, and ZooKeeper installed.

    Same-node Solr plus SolrCloud

Here are installation instructions for Unix and Windows.

  • Cluster arrangement 5: ZooKeeper cluster on Fusion nodes & external SolrCloud cluster – Fusion and ZooKeeper are installed on the first three nodes in the Fusion cluster. If you add more Fusion nodes, they don’t need ZooKeeper. Fusion uses an external SolrCloud cluster for both data (for example, signals, aggregated signals, and indexes) and logs.

    Same-node ZooKeeper plus external SolrCloud

Here are installation instructions for Unix and Windows.