When you are deploying a single-instance system, that instance is automatically configured as a master instance and runs all services for the system. The following instructions for installing a single-instance of Pentaho Worker Nodes includes the following steps.
- Configure the server or virtual machine
- Run Docker on each server or virtual machine
- Unpack the Pentaho Worker Nodes product package
- Running the setup script
- Start the application on the server or virtual machine
- Deploy the System
Configure the server or virtual machine
Configure the mmap count. Add this line to the /etc/sysctl.conf file:
vm.max_map_count = 262144NoteIf the line already exists, verify that the value is greater than or equal to ‘262144’.
Configure the firewall rules to allow communication over all network ports that your system requires.NoteFor information on the ports that your system requires, see Networking.
Restart the server or virtual machine.
Run Docker on each server or virtual machine
For example, to run Docker using systemd, do the following.
To check if Docker is running, run the following command.systemctl status docker
If Docker is not running, start the Docker service.sudo systemctl start docker
(Optional) Configure the Docker service to start automatically when you restart the server or virtual machine.sudo systemctl enable docker
Unpack the Pentaho Worker Nodes product package
Retrieve the pentaho-workernodes-.tgz file and store it in a directory on the server or virtual machine.
In the largest disk partition, create a directory called /pwn or a directory name of your choice.The command mkdir /<path>/pwn creates the /pwn directory in/opt
Move the installation package to the /pwn directory:mv <path>/pentaho-workernodes-<prod-version-number>.tgz/<path>/pwn
Navigate to the installation directory:cd /<path>/pwn
Unpack the installation package:sudo tar -zxf pentaho-workernodes-<prod-version-number>.tgz
Run the install script in the version-specific directory:sudo ./cluster/<platform-version>/bin/install
For example: sudo ./cluster/1.5.0-142/bin/install
Running the setup script
The external network IP address for the instance that you are running the script on.
The internal network IP address for the instance that you are running the script on.
Comma-separated list of external network IP addresses of each master instance.
Comma-separated list of internal network IP addresses of each master instance.
If you are enabling secure communication, you need all four of the above options. Use the following table to determine which options you need to use for your single-instance system:
|Number of instances in the system
|Network type usage
|Single network type for all services
|Use -i only
|External for all services
|Use -i only
|Internal for some services, external for others
|Use both -i and -I, and both -m and -M. Both upper- and lower-case parameter values are required. Also, a master instance must be set for secure mode.
- Non-secure single-instance system:
sudo bin/setup -i 192.0.2.4
- Secure multi-instance system:
sudo bin/setup -i 192.0.2.4 -I 192.0.2.4 -m 192.0.2.4,192.0.2.3,192.0.2.2 -M 192.0.2.4,192.0.2.3,192.0.2.2
The bin/setup command uses the lower-case parameters (-i and -m) for the external IP values and the upper-case parameters (-I and -M) for the internal IP values.
Start the application on the server or virtual machine
On each server or virtual machine that will host the Pentaho Worker Nodes instance, start the run application script using your usual methods for running scripts.
The following are some examples of how you can start the script.
Example 1: Run the script in the foreground
Run the following command:sudo bin/run
When you run the script using this method, the script does not automatically complete. It remains running in the foreground.
Example 2: Run the script as a service using systemd
If you have installed the Pentaho Worker Nodes product in a directory other than the default location, then edit theFor example, in
pentahoWorkerNodes.servicefile to point to that location.
/<file-path>/bin/pentahoWorkerNodes.service, set the ExecStart parameter to the directory location as follows:
pentahoWorkerNodes.servicefile to the appropriate location for your operating system, such as:
cp /<file-path>/bin/pentahoWorkerNodes.service /etc/systemd/system
Enable and start the search service as follows:sudo systemctl enable pentahoWorkerNodes.service
sudo systemctl start pentahoWorkerNodes.serviceNoteWhen you activate the search service,
systemctlmay display the following message:
The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...)
Depending on your OS, the search service may or may not have been enabled successfully. To avoid this situation, verify that you moved the
pentahoWorkerNodes.serviceto the applicable location, which is typically
Deploy the System
Open a web browser and go to
https://<instance-IP-address>:8000.NoteYou must enter https. You must also click through one or more security warnings.
On the Welcome page, set a password for the initial admin user account, then click Set Admin Password. The Confirm Cluster Topology page displays all detected instances.
If your system includes multiple instances, verify that all expected instances are listed. If they are not, click on the link in the Instance Discovery panel until they appear.
(Optional) If you want to change networking settings for the services, perform the following steps:NoteIf you want to reconfigure networking for the Pentaho Worker Nodes services, you must do so now before deploying the system.
Click the link in the Advanced Network Configuration section.
(Optional) For each service, configure the ports that the service should use.NoteIf you reconfigure service ports, verify that each port value you assign is unique across all services, both System services and Pentaho Worker Nodes services.
(Optional) For each service, specify which network the service should bind to, either Internal or External.NoteBy default, the Search-App and Admin-App services have the External option selected and all other services are set to Internal.If you are only using a single network, you can leave these settings as they are since all system instances are assigned both internal and external IP addresses. If you are only using a single network type, the internal and external IP addresses for each instance are identical.
For more information, see Networking.
Click the Deploy Single Instance or Deploy Cluster button. The system deployment starts. You can click on the View Deployment Details link to view the progress of the deployment.
You cannot change networking settings for System services at this point. However,
if you configured the System services networking incorrectly, the Administration App may fail
to appear. This failure may happen if the
network.config file is not
identical on all instances. For error information, view the
file or the output information logged by the run script.
Next, you should check your network settings.
Check your networking settings
Stop the run script from running by using the method you are currently using to run the script.
Run this command to stop all Docker containers on the instance:sudo systemctl stop pentahoWorkerNodes.service
Delete the contents of the
<install-path>/pwn/directory from all instances.
Begin the installation again from Unpack the Pentaho Worker Nodes product package
Next step: Set up mounted volumes
After installing Pentaho Worker Nodes, see Setting up mounted volumes on Pentaho Worker Nodes to continue the setup process.