Installing Big Match on Cloudera

After downloading the installer artifacts, run the executable on the node where you have the Cloudera server installed.

Procedure

Update the permissions on the downloaded *.bin file to enable execute.
```
chmod +x <package_name>.bin
```
Run the *.bin file to extract and install the services in the module.
```
./bigmatch_<project_version>.bin
```
Note: Run the *.bin file on a Linux system because this file depends on some system packages.
After the prompt, agree to the license terms. Reply yes | y to continue with the install.
After the prompt, choose if you want to install Big Match online (Option 1), or offline (Option 2).

Option 1: Hadoop cluster has access to the internet

The program will lay out the Cloudera service configuration files and update the repository locations in the Ambari server file, repoinfo.xml.

Skip to step 6.

Option 2: Hadoop cluster does not have access to the internet

This option initiates a download of files to set up a local repository mirror. A subdirectory called BigMatch is created and RPMs with the associated files are located in directory BigMatch/packages.
Set up a local repository. A local repository is required if the Hadoop cluster cannot connect directly to the internet.

Note: If the bin file was executed on a node not in the Hadoop cluster, then the files in BigMatch/packages should be copied over to the node running Cloudera Manager Server prior to running the following steps.
By selecting Option 2 in step 4, Big Match Cloudera files were downloaded to a subdirectory called BigMatch/packages. Unzip them, then run the following commands to copy the files listed below to the appropriate destinations.
```
cp BigMatch/packages/bigmatch_binaries/*.parcel    /opt/cloudera/parcel-repo/
```
```
cp BigMatch/packages/bigmatch_binaries/*.sha /opt/cloudera/parcel-repo/
```
```
cp BigMatch/packages/bigmatch_binaries/*.jar    /opt/cloudera/csd/
```
Note: /opt/cloudera/parcel-repo and /opt/cloudera/csd are the default directories for the Cloudera local parcel repository directory and CSDs. If your cluster is configured with non-default locations, you must adjust these commands accordingly.
Verify that the owner and group of the CSD file located in the CSD directory is set to cloudera-scm. If the owner and group of the CSD file is not cloudera-scm, then run the following command to correct the ownership:
```
chown cloudera-scm:cloudera-scm
        /opt/cloudera/csd/bigmatch-cloudera-csd-11.5.0.4-el*.jar
```
(Where /opt/cloudera/csd is the CSD directory. This path may differ in your installation, as described in the previous step.)
Restart Cloudera Manager by executing the following command:
```
sudo service cloudera-scm-server restart
```
This will ensure that the CSD you just added is picked up by Cloudera Manager.
In the Cloudera Manager UI, click the Parcels icon on the top right. If you're using Option 1 from step 4, click the Download button for the Big Match Parcel. Then, for both Option 1 and Option 2, click Distribute. This will distribute the contents of the parcel to the nodes in the cluster. Once distributed, click Activate to activate the Big Match Parcel. This simply creates a symbolic link named after the service pointing it to the parcel directory which takes the form of service name followed by version.
Configure a node to have password-less ssh access as root to all nodes in the cluster.
Execute the following script on this node $PARCEL_DIR/BIGMATCH/bin/install.sh where $PARCEL_DIR is the Parcel directory for your cluster. This directory is by default located at /opt/cloudera/parcels however, you can change the location in the Cloudera Manager UI to point to a custom path.

Note: The above locations are the default locations of parcel and CSDs but can be configured in Cloudera Manager.

Note: A log will be generated at /tmp/BigMatchInstall-<timestamp>.log and also be output to the console. Ensure that there are no ERROR messages before continuing to the next step.
Restart any services that require it due to stale configuration. Services with stale configurations will be notated in the cluster view in Cloudera Manager UI. Clicking the Redeploy icon will bring up a screen showing all the stale configurations and let you restart these services in bulk.
In the Cloudera Manager UI under the Cloudera Manager Home screen, click Add Service in the Cluster drop-down to add the Big Match Service to the cluster. The Cloudera Manager Service Installation Wizard will prompt you for all necessary information.