Standalone FS Analytics
Follow these steps to run FS Analytics on separate Pulse components on separate nodes:
Follow same steps as performed earlier with Install Pulse on a Single Node (Docker)
Create config directory with command
accelo admin makeconfig ad-fsanalyticsv2-connector
and add/update following details in environment section:- MONGO_URI (Acceldata team will provide the right URI)
- MONGO_ENCRYPTED=false
- ES_HOST=<host_running_ES>
- ES_PORT=19013
Append below 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
)- <PULSE_CORE_HOST> ad-streaming
For Kerberized cluster, update following contents in mentioned files:
Change directory to
<ACCELO_HOME>/config/krb/security/
and add/update following files:- Add required hdfs user keytab as per prerequisite under the current directory
- Update
krb5.conf
andkrb5JAASLogin.conf
files as per the keytab principal name and file name
Modify file present under
<ACCELO_HOME>/work/<cluster_name>/fsanalytics/kinit_fsimage.sh
- Add kinit command -
kinit -kt /krb/security/<keytab_file_name> <principal_name>
- Update
IsKerberosEnabled=1
- Add kinit command -
Run below command, type the active cluster name, and select FS Analytics V2 as mentioned in below 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
- Press the enter key to start.
FS Analytics is now running on separate Pulse components on different nodes.