Start and Stop Fusion

This topic explains how to start and stop Fusion.

Unix

This section describes starting and stopping Fusion on Unix.

Starting Fusion

All Fusion start scripts must be executed by a user who has permissions to read and write to the directories where Fusion is installed. These scripts don’t need to be run as root (or sudo), nor should they be. Use a suitable ID, or create a new one, and then ensure that it owns the directory where Fusion resides, (e.g. /opt/lucidworks).

To start all required services

./bin/fusion start

To start services individually
  • Fusion API Services:

    ./bin/api start

  • Connectors Services:

    ./bin/connectors start

  • Solr:

    ./bin/solr start

  • Spark Master:

    ./bin/spark-master start

  • Spark Worker:

    ./bin/spark-worker start

  • Fusion UI:

    ./bin/ui start

  • ZooKeeper:

    ./bin/zookeeper start

For information about default ports, see Default Ports.

Running Fusion In The Foreground

To run Fusion or any of its services in the foreground, use the run command-line argument in place of start.

Stopping Fusion

To stop Fusion or any of its services, use the stop command-line argument in place of start.

Ubuntu Upstart Scripts

Under Ubuntu 12.04 LTS or newer we support Upstart for process management. This requires Fusion to be installed in the /opt/lucidworks/ directory.

To configure upstart, run the following commands:

$ cd init/upstart
$ sudo bash install.sh

If this complains with no JAVA_HOME set, replace sudo with sudo -E. Then you can use the service command to control the server:

$ sudo service fusion-solr start
$ sudo service fusion-api start
$ sudo service fusion-connectors start
$ sudo service fusion-ui start

and similarly use stop and status.

Logfiles for Fusion services are found in directories under fusion/3.1.x/var/log.

Windows

This section describes starting and stopping Fusion on Windows.

Starting Fusion

All Fusion start scripts must be executed by a user who has permissions to read and write to the directories where Fusion is installed. Ensure that such a user owns the directory where Fusion resides.

To start all required services
  • bin\fusion.cmd start

  • bin\start-services.cmd (Start all Fusion services as Windows services)

To start services individually
  • Fusion API Services:

    bin\api.cmd start

  • Connectors Services:

    bin\connectors.cmd start

  • Solr:

    bin\solr.cmd start

  • Spark Master:

    bin\spark-master.cmd start

  • Spark Worker:

    bin\spark-worker.cmd start

  • Fusion UI:

    bin\ui.cmd start

  • Zookeeper:

    bin\zookeeper.cmd start

For information about default ports, see Default Ports.

Running Fusion In The Foreground

To run Fusion or any of its services in the foreground, use the run command-line argument in place of start.

Stopping Fusion

To stop Fusion or any of its services, use the stop command-line argument in place of start.

Accessing the system after startup

Once the services have been started, you can access the Fusion UI at http://localhost:8764/ (replace 'localhost' with your server name or IP if needed). The first time you access the system, you must first set the admin password and agree to the Fusion terms. This is followed by an optional registration step. After this, Fusion displays the main UI page.

If you can’t access the system, see the Troubleshooting section below. Checking System State shows how to inspect Fusion services.