Like what you see? Have a play with our trial version.

As a Yellowfin cluster requires only one database instance, it means that the Yellowfin installation process will differ slightly when installing a cluster. The first Yellowfin cluster node can be installed the same way as a standalone instance of Yellowfin. The command-line or GUI installer can be used.

Additional Yellowfin Cluster nodes do not require the Yellowfin database.  There are several ways for installing additional nodes:

No Database Access Installation

After the initial node is installed, and the Yellowfin database is created, the Yellowfin installer can be used for the installation of subsequent nodes without affecting the initial database.

Use the Yellowfin Installer using the command:

java -jar yellowfin-20170928-full.jar action.nodbaccess=true

The action.nodbaccess=true option will run the installer as usual, and prompt for database credentials, but not create or alter the database during installation. This will only generate the filesystem component of Yellowfin. If Legacy Clustering is used, individual changes may need to be made to the web.xml file on each of the nodes.

File System Replication

As the filesystem structure on each node is the same, a new node can be created by duplicating the Yellowfin installation directory onto another computer. If Legacy Clustering is used, changes will need to be made to the web.xml file on each node.

Virtual Machine Replication

A Virtual Machine (or AWS AMI or Azure Compute image or Docker image) could be pre-configured with the Application Server component of Yellowfin. A copy of the Virtual Machine could be started for each application node in a cluster.

Previous topic: Clustering overview

  • No labels