Deploy FS Analytics on a Separate Node

Follow these steps to run FS Analytics on separate Pulse components on separate nodes:

Follow the same steps as performed earlier with Install Pulse on Single Node (Docker/Podman-Based)

1. Create a config directory with command accelo admin makeconfig ad-fsanalyticsv2-connector and add/update following details in environment section:

2. 1. MONGO_URI (Acceldata team will provide the right URI)
   2. MONGO_ENCRYPTED=false
   3. ES_HOST=<host_running_ES>
   4. ES_PORT=19013

3. Append the hostname entry in /etc/hosts and check if the /etc/hosts file is mounted under volume section in above created file (<ACCELO_HOME>/config/docker/addons/ad-fsanalyticsv2-connector.yml)

   1. <PULSE_CORE_HOST> ad-streaming

4. For the Kerberized cluster, update the following contents in the mentioned files:

   1. Change directory to <ACCELO_HOME>/config/krb/security/ and add/update the following files:

      1. Add the required HDFS user keytab as per the prerequisite under the current directory
      2. Update krb5.conf and krb5JAASLogin.conf files as per the keytab principal name and file name

   2. Modify the file present under <ACCELO_HOME>/work/<cluster_name>/fsanalytics/kinit_fsimage.sh

      1. Add kinit command - kinit -kt /krb/security/<keytab_file_name> <principal_name>
      2. Update IsKerberosEnabled=1

5. Run the command below, type the active cluster name, and select FS Analytics V2 as mentioned in the steps.

[root@pulse2:~ (ad-default)]$ accelo deploy addons

INFO: Active Cluster:  pulse_demo

? Select the SA components you would like to install:   [Use arrows to move, space to select, type to filter]

> [ ]  FS Elastic

  [ ]  LogSearch

  [ ]  STANDALONE TSDB

  [x]  FS Analytics V2

  [ ]  STANDALONE DB

  [ ]  HA GraphQL

  [ ]  LDAP

6. Press the enter key to start.

FS Analytics is now running on separate Pulse components on different nodes.