CDP Deployment for Single KDC

This document provides a step by step process to deploy single Pulse instance for Cloudera clusters with single KDC.

Prerequisites

Keep the following information handy:

CM URL (https://<Alias/FQDN of the CM URL>:<CM Port>)
CM Username
CM Password
Spark History HDFS path & Spark3 History HDFS path
Kafka Version
Hbase Version
Hive Version
Hive Metastore DB Connection URL
hive metastore Database Name
hive metastore DB Username
hive metastore DB Password
Oozie DB Name
Oozie DB URL
Oozie DB Username
Oozie DB Password
Kerberos Keytab
krb5.conf file
Principal
Kerberos Username
cacerts/jssecacerts
YARN Scheduler Type
Kafka Interbroker protocol

Prerequisites for enabling (TLS) HTTPS for Pulse web UI configuration:

Certificate File: cert.crt
Certificate Key: cert.key
CA Certificate: ca.crt (optional)
Decide whether to keep the HTTP port (Default: 4000) open or not
Decide on which port to use (default: 443)

Uninstallation

For uninstalling agents, you must follow the Cloudera Parcel Agent Uninstall doc.
You must also remove the Pulse JARS and the configuration for Hive and Tez.
Acceldata will then perform the following command for backup and uninstalling the existing Pulse.

a. Create a backup directory.

mkdir -p /data01/backup

b. For backup, we can copy the whole config and work dir.

cp -R $AcceloHome/config /data01/backup/ cp -R $AcceloHome/work /data01/backup/

c. Uninstall the existing Pulse setup by running the following command:

accelo uninstall local

OUTPUT

[root@nifihost1:data01 (ad-default)]$ accelo uninstall local ✗ You're about to uninstall the local AccelData setup. This will also DELETE all persistent data from the current node. However, NONE of the remote no ✔ You're about to uninstall the local AccelData setup. This will also DELETE all persistent data from the current node. However, NONE of the remote no ✔ You're about to uninstall the local AccelData setup. This will also DELETE all persistent data from the current node. However, NONE of the remote no You're about to uninstall the local AccelData setup. This will also DELETE all persistent data from the current node. However, NONE of the remote nodes will be affected. Please confirm your action [y/n]: : y WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB Uninstalling the AccelData components from local machine ...

d. Logout from the terminal session.

Download the Binaries and Docker Images and Load Them

Download the jars, hystaller, accelo binaries, and docker images from the download links provided by Acceldata.
Move the docker images and jars in the following directory:

mkdir -p /data01/images

Copy the binaries and tar files in to the /data01/images folder.

cp </path/to/binaries/tar> /data01/images

Change the directory.

cd /data01/images

Extract the single tar file.

tar xvf <name_of_tar_file>.tar

OUTPUT

[root@nifihost1 images]# tar xvf pulse-333-beta.tar ./ad-alerts.tgz ./ad-connectors.tgz ./ad-dashplots.tgz ./ad-database.tgz ./ad-deployer.tgz ./ad-director.tgz ./ad-elastic.tgz ./ad-events.tgz ./ad-fsanalyticsv2-connector.tgz ./ad-gauntlet.tgz ./ad-graphql.tgz ./ad-hydra.tgz ./ad-impala-connector.tgz ./ad-kafka-0-10-2-connector.tgz ./ad-kafka-connector.tgz ./ad-ldap.tgz ./ad-logsearch-curator.tgz ./ad-logstash.tgz ./ad-notifications.tgz ./ad-oozie-connector.tgz ./ad-pg.tgz ./ad-pulsemon-ui.tgz ./ad-recom.tgz ./ad-sparkstats.tgz ./ad-sql-analyser.tgz ./ad-streaming.tgz ./ad-vminsert.tgz ./ad-vmselect.tgz ./ad-vmstorage.tgz ./accelo.linux ./admon ./hystaller

Load the Docker images by running the following command:

ls -1 *.tgz | xargs --no-run-if-empty -L 1 docker load -i

Check if all the images are loaded into the server.

docker images | grep 3.3.3

Config Cluster

Validate the all the hosts file.
Create the acceldata dir by running the following command:

cd /data01/ mkdir -p acceldata

Copy the Spark hosts and Zookeeper hosts file in acceldata directory, by running the following command:

cp </path/to/hosts_files> /data01/acceldata

Place the accelo binary in the /data01/acceldata directory.

cp </path/to/accelo/binary> /data01/acceldata

Rename the accelo.linux binary to accelo.

mv /data01/acceldata/accelo.linux accelo chmod +x /data01/acceldata/accelo

Change the directory.

cd /data01/acceldata/accelo

Run the following command to do accelo init :

./accelo init

Enter the appropriate answers when prompted.
Source the ad.sh file.

source /etc/profile.d/ad.sh

Run the init command to provide the Pulse version.

accelo init

OUTPUT

[root@nifihost1:~ (ad-default)]$ accelo init Enter the AccelData ImageTag: : 3.3.3 ✓ Done, AccelData Init Successful.

Provide the correct Pulse version, in this case it will be 3.3.3.

Now run accelo info command to get the initial info.

accelo info

OUTPUT

[root@nifihost1:~ (ad-default)]$ accelo info WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB ___ ____________________ ____ ___ _________ / | / ____/ ____/ ____/ / / __ \/ |/_ __/ | / /| |/ / / / / __/ / / / / / / /| | / / / /| | / ___ / /___/ /___/ /___/ /___/ /_/ / ___ |/ / / ___ | /_/ |_\____/\____/_____/_____/_____/_/ |_/_/ /_/ |_| Accelo CLI Version: 3.3.3-beta Accelo CLI Build Hash: 8ba4727f11e5b3f3902547585a37611b6ec74e7c Accelo CLI Build ID: 1700746329 Accelo CLI Builder ID: ZEdjMmxrYUdGdWRGOWhZMk5sYkdSaEVLCg== Accelo CLI Git Branch Hash: TXdLaTlCVDFBdE56STNvPQo= AcceloHome: /data01/acceldata AcceloStack: ad-default AccelData Registry: 191579300362.dkr.ecr.us-east-1.amazonaws.com/acceldata AccelData ImageTag: 3.3.3-beta Active Cluster Name: NotFound AcceloConfig Mongo DB Retention days: 15 AcceloConfig Mongo DB HDFS Reports Retention days: 15 AccelConfig TSDB Retention days: 31d Number of AccelData stacks found in this node: 0

Run the config cluster command to configure the cluster in Pulse.

accelo config cluster

Provide appropriate answers when prompted.

[root@pulsecdp01:acceldata (ad-default)]$ accelo config cluster INFO: Configuring the cluster ... INFO: Using default API Version v10 for CM API Is the 'Database Service' up and running? [y/n]: : n WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB ✔ Cloudera Enter Your Cluster's Display Name: : cdp1 Enter Cloudera URL (with http/https): : https://cdpssl01.acceldata.dvl:7183 ✔ Enter Cloudera Username: : admin█ IMPORTANT: This password will be securely encrypted and stored in this machine. Enter Cloudera User Password: : ***** Enter the cluster name to use (MUST be all lowercase & unique): : cdp1 ERROR: stat /data01/acceldata/.activecluster: no such file or directory INFO: Creating Post dirs. ✔ Cluster1 INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API INFO: Using lower case for CDP Service name API Enter the installed Kafka version (ex: 0.10.2): : 0.11.0 : 0.11.0█ Enter the installed HBase service version (ex: 0.9.4): : 0.9.4 Enter the installed Hive service version (ex: 2.0.0): : 2.0.0 Enter the installed Hive service version (ex: 2.0.0): : 2.0.0 ✓ Found Kerberos Realm: ADSRE.COM Enter the Spark History HDFS path: : /user/spark/applicationHistory Oozie DB URL: : jdbc:postgresql://cdpssl01.acceldata.dvl:7432/oozie_oozie_server ✔ Oozie DB URL: : jdbc:postgresql://cdpssl01.acceldata.dvl:7432/oozie_oozie_server█ Enter the Oozie DB Username: : oozie_oozie_server Enter the Oozie DB Password: : ********** Enter the Oozie DB JODA Timezone (Example: Asia/Kolkata): : Asia/Kolkata ✔ Enter the hive metastore Database Name : : hive█ ✔ Hive Metastore PostgreSQL DB Connection URL: : jdbc:postgresql://cdpssl01.acceldata.dvl:7432/hive█ Enter the hive metastore DB Username : : hive ✔ Enter the hive metastore DB Password : : **********█ ✔ Enter the hive metastore DB Password : : **********█ INFO: core-site.xml file has been updated INFO: hdfs-site.xml file has been updated ---------------------------Discovered configurations---------------------------------------- ✓ Cluster Type: CDH ✓ CDH Version: 7.1.7 ✓ Discovered Cluster Name: cdp1 ✓ Discovered Services: ✓ PULSEHYDRAAGENT ✓ SOLR ✓ SPARK_ON_YARN ✓ KAFKA ✓ LIVY ✓ HUE ✓ HIVE_ON_TEZ ✓ HBASE ✓ QUEUEMANAGER ✓ RANGER ✓ IMPALA ✓ ATLAS ✓ ZOOKEEPER ✓ OOZIE ✓ HIVE ✓ YARN ✓ HDFS ✓ Yarn RM URI: https://cdpssl02.acceldata.dvl:8090,https://cdpssl03.acceldata.dvl:8090 ✓ MapReduce Job History URI: https://cdpssl02.acceldata.dvl:19890 ✗ Yarn ATS is not enabled ✓ HDFS Namenode URI: swebhdfs://nameservice1 ✓ Hive Metastore URI: thrift://cdpssl02.acceldata.dvl:9083 ✗ Hive LLAP is not enabled ✓ Spark History Server URIs: https://cdpssl02.acceldata.dvl:18488 ✓ Impala URI: http://cdpssl04.acceldata.dvl:25000,http://cdpssl05.acceldata.dvl:25000,http://cdpssl01.acceldata.dvl:25000 ✓ Kafka Broker URI: https://cdpssl04.acceldata.dvl:9093,https://cdpssl05.acceldata.dvl:9093,https://cdpssl03.acceldata.dvl:9093 ✓ Zookeeper Server URI: http://cdpssl01.acceldata.dvl:2181,http://cdpssl02.acceldata.dvl:2181,http://cdpssl03.acceldata.dvl:2181 Would you like to continue with the above configuration? [y/n]: : y Is Kerberos enabled in this cluster? [y/n]: : y ✓ Found Kerberos Realm: ADSRE.COM Enter your Kerberos keytab username (Must have required HDFS permissions): : hdfs INFO: min-reports is set to default value 10 INFO: Purging old config files ✓ acceldata.conf file generated successfully. Setting up Kerberos Config Setting up kerberos.. Enter the principal: : hdfs/cdpssl03.acceldata.dvl@ADSRE.COM Enter full path to the Keytab file (eg: /root/hdfs.keytab): : /data01/security/kerberos_cluster1.keytab Enter the krb5Conf file path: : /data01/security/krb5_cluster1.conf WARN: /data01/acceldata/config/users/passwd already being generated ✓ Done, Kerberos setup completed. INFO: Creating post config files INFO: Writing the .dist files INFO: Clustername : cdp1 INFO: Performing PreCheck of Files Is HTTPS Enabled in the Cluster on UI Endpoint? [Y/N]: : Y Enter the Java Keystore cacerts File Path: : /data01/security/cacerts Enter the Java Keystore jsseCaCerts File Path: : /data01/security/cacerts INFO: Setting the active cluster WARN: Cannot find the pulse.yaml file, getting the values from acceldata.conf file WARN[1090] cannot find the spark on yarn thriftserver service ports WARN[1090] Atlas Server not installed WARN[1090] Hive Server Interactive not installed Creating hydra inventory ✔ Is the agent deployment Parcel Based? [Y/N] : : Y█ pulsecdp01.acceldata.dvl is the hostname of the Pulse Server, Is this correct? [Y/N]: : y ? Select the components you would like to install: Impala, Metastore, Hdfs, HiveServer2, Zookeeper, Yarn, Hbase Is Kerberos Enabled for Impala?: y Enter the JMX Port for hive_metastore: : 8009 ✔ Enter the JMX Port for zookeeper_server: : 9010█ Enter the Kafka Broker Port: : 9092 Do you want to enable Impala Agent: [Y/N]? : Y Would you like to setup LogSearch? [y/n]: : y ? Select the logs for components that are installed/enabled in your target cluster: kafka_server, yarn_timelinereader, impala_catalogd, yarn_timelineserver, hue_runcpserver, hive_server, oozie_jpa, ranger_audit, yarn_resourcemanager, hdfs_audit, oozie_error, hbase_regionserver, hue_error, impala_impalad, hdfs_datanode, yarn_nodemanager, mapred_historyserver, hbase_master, kafka_state_change, hdfs_namenode, kafka_server_gc, kafka_controller, kafka_err, yarn_application, kafka_log_cleaner, hive_server_interactive, oozie_audit, zookeeper, oozie_tomcat, hue_migrate, hue_access, syslog, oozie_ops, oozie_server ✓ Generated the vars.yml file successfully INFO: /data01/acceldata/work/cdp1/fsanalytics/update_fsimage.sh - ✓ Done INFO: /data01/acceldata/work/cdp1/fsanalytics/kinit_fsimage.sh - ✓ Done INFO: /data01/acceldata/work/cdp1/fsanalytics/update_fsimage_csv.sh - ✓ Done Configuring notifications ✓ Generated the notifications.yml file successfully Configuring notifications ✓ Generated the actions notifications.yml file successfully INFO: Please run 'accelo deploy core' to deploy APM core using this configuration.

Copy the License

Place the license file provided by Acceldata in the work directory.

cp </path/to/license> /data01/acceldata/work

Deploy Core

Deploy the Pulse core components by running the following command:

accelo deploy core

OUTPUT

[root@nifihost1:acceldata (ad-default)]$ accelo deploy core ERROR: Cannot connect to DB, Because: cannot connect to mongodb WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB Have you verified the acceldata config file at '/data01/acceldata/config/acceldata_spark341.conf' ? [y/n]: : y ✓ accelo.yml file found and parsed ✓ AcceloEvents - events.json file found and parsed ✓ acceldata conf file found and parsed ✓ .dist file found and parsed ✓ hydra_hosts.yml file found and parsed ✓ vars.yml file found and parsed ✓ alerts notification.yml file found and parsed ✓ actions notification.yml file found and parsed ✓ alerts default-endpoints.yml file found and parsed ✓ override.yml file found and parsed ✓ gauntlet_mongo_spark341.yml file found and parsed ✓ gauntlet_elastic.yml file found and parsed INFO: No existing AccelData networks found. Current stack 'ad-default' is missing. INFO: Trying to create a new network .. INFO: If you're setting up AccelData for the first time give 'y' to the below. Would you like to initiate DB with the config file '/data01/acceldata/config/acceldata'? [y/n]: : y Creating group monitors [================================================================================================>-------------------] 83.33%INFO: Pushing the hydra_hosts.yml to mongodb Deployment Completed [==============================================================================================>--------------------] 81.82% 28s ✓ Done, Core services deployment completed. Now, you can access the AccelData APM Server at the configured port of this node. To deploy the AccelData addons, Run './accelo deploy addons'

Configure SSL Certificate for Pulse Services

If you have TLS/SSL enforced for any of the Hadoop components in the target cluster, you need to place the certificate and certificate password files in the cd /data01/acceldata/config/security path.

For details, see Manage SSL Certificates for Pulse Services and Connectors.

Deploy Addons

Run the following command to deploy the Pulse addons, and then select the components that are needed for Spark standalone:

accelo deploy addons

OUTPUT

[root@nifihost1:acceldata (ad-default)]$ accelo deploy addons WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB INFO: Active Cluster: spark341 ? Select the components you would like to install: Alerts (Agents MUST be configured), Core Connectors, Dashplot, Director (Agents MUST be configured), HYDRA, LogSearch, Notifications Starting the deployment .. Completed [==============================================================================================================================] 137.50% 29s ✓ Done, Addons deployment completed.

Configure Alerts Notifications

For setting the active cluster, run the following command:

accelo set

Configure the alerts notifications.

accelo config alerts notifications

OUTPUT

[root@nifihost1:acceldata (ad-default)]$ accelo config alerts notifications Enter the JODA Timezone value (Example: Asia/Jakarta): : Asia/Kolkata ? Select the metric groups you would like to enable: druid, nifi, ntpd, anomaly, chrony, customApp ? Select the notifications you would like to enable: email INFO: Configuring Email Notifications: Enter Email DefaultToEmailIds (comma separated list): : Enter Email DefaultSnoozeIntervalInSecs: : 0 Enter Email MaxEmailThreshold: : 1 ✓ Done, Alerts Notifications Configuration file generated ✓ Done, Alerts Notifications pushed to Pulse DB

Set the cluster2 as the active cluster.

accelo set

Configure the alerts for the second cluster.

Set the cluster3 as the active cluster.

accelo set

Configure the alerts for the third cluster.

[root@nifihost1:acceldata (ad-default)]$ accelo config alerts notifications Enter the JODA Timezone value (Example: Asia/Jakarta): : Asia/Kolkata ? Select the metric groups you would like to enable: druid, nifi, ntpd, anomaly, chrony, customApp ? Select the notifications you would like to enable: email INFO: Configuring Email Notifications: ✔ Enter Email DefaultSnoozeIntervalInSecs: : 0█ mEnter Email MaxEmailThreshold: : 11█ ✔ Enter Email MaxEmailThreshold: : 1█ ✓ Done, Alerts Notifications Configuration file generated ✓ Done, Alerts Notifications pushed to Pulse DB

Restart the alerts notifications.

accelo restart ad-alerts

OUTPUT

[root@nifihost1:spark341 (ad-default)]$ accelo restart ad-alerts WARN: Gauntlet is running in dry run mode. Disable this to delete indices from elastic and purge data from mongo DB ✗ You're about to restart AccelData services. This will restart all or any specified the service. However, any persistent data will be left untouched. ✔ You're about to restart AccelData services. This will restart all or any specified the service. However, any persistent data will be left untouched. ✔ You're about to restart AccelData services. This will restart all or any specified the service. However, any persistent data will be left untouched. You're about to restart AccelData services. This will restart all or any specified the service. However, any persistent data will be left untouched. Please confirm your action [y/n]: : y Completed [===============================================================================================================================] 100.00% 1s Restart ad-alerts completed ✓

Database Push Configuration

Run the following command to push config to db:

accelo admin datbase push-config -a

Configure Gauntlet

Updating the Gauntlet Crontab Duration

Check if the ad-core.yml file is present or not by running the following command:

ls -al $AcceloHome/config/docker/ad-core.yml

If the above file is not present, then generate it by running the following command:

accelo admin makeconfig ad-core

Edit the ad-core.yml file.

a. Open the file.

vi $AcceloHome/config/docker/ad-core.yml

b. Update the CRON_TAB_DURATION env variable in the ad-gauntlet section.

CRON_TAB_DURATION=0 0 */2 * *

This makes gauntlet run every two days at midnight.

c. The updated file will look something like this:

ad-gauntlet: image: ad-gauntlet container_name: ad-gauntlet environment: - MONGO_URI=ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXosC8vfVkGYGWGPNnX64ZVSp9yHgErQknPBAfYZ9cOG1A== - MONGO_ENCRYPTED=true - ELASTIC_ADDRESSES=http://ad-elastic:9200 - DRY_RUN_ENABLE=true - CRON_TAB_DURATION=0 0 */2 * * volumes: - /etc/localtime:/etc/localtime:ro - /root/acceldata/config/logsearch/gauntlet_elastic.yml:/gauntlet/config/config.yml - /root/acceldata/logs/logsearch/:/gauntlet/logs/ ulimits: {} ports: [] depends_on: [] opts: {} restart: "" extra_hosts: [] network_alias: []

d. Save the file.

Restart gauntlet service by running the following command:

accelo restart ad-gauntlet

Updating the Gauntlet Dry Run Mode

Check if the ad-core.yml file is present or not by running the following command:

ls -al $AcceloHome/config/docker/ad-core.yml

If the above file is not present, then generate it by running the following command:

accelo admin makeconfig ad-core

Edit the ad-core.yml file.

a. Open the file.

vi $AcceloHome/config/docker/ad-core.yml

b. Update the DRY_RUN_ENABLE env variable in the ad-gauntlet section.

DRY_RUN_ENABLE=false

This will make the gauntlet delete the older elastic indices and MongoDB data.

c. The updated file will look something like this:

ad-gauntlet: image: ad-gauntlet container_name: ad-gauntlet environment: - MONGO_URI=ZN4v8cuUTXYvdnDJIDp+R8Z+ZsVXXjv8zDOvh8UwQXosC8vfVkGYGWGPNnX64ZVSp9yHgErQknPBAfYZ9cOG1A== - MONGO_ENCRYPTED=true - ELASTIC_ADDRESSES=http://ad-elastic:9200 - DRY_RUN_ENABLE=false - CRON_TAB_DURATION=0 0 */2 * * volumes: - /etc/localtime:/etc/localtime:ro - /root/acceldata/config/logsearch/gauntlet_elastic.yml:/gauntlet/config/config.yml - /root/acceldata/logs/logsearch/:/gauntlet/logs/ ulimits: {} ports: [] depends_on: [] opts: {} restart: "" extra_hosts: [] network_alias: []

d. Save the file.

Restart gauntlet service by running the following command:

accelo restart ad-gauntlet

Configuring Gauntlet for Multi Node and Multi Cluster Deployment

Run the following command to generate the gauntlet config files:

accelo admin database push-config -s -a

Change the dir to config/gauntlet/ .

cd $AcceloHome/config/gauntlet

Check if all the files are present or not for all the clusters or not.

[root@cdp5007:gauntlet (ad-default)]$ accelo admin database push-config -a -s Is the 'Database Service' up and running? [y/n]: : y INFO: Working on cluster: cl1 Creating group monitors [========================================================================================================================================================================================================>----------------------------------------] 83.33%INFO: Pushing the hydra_hosts.yml to mongodb INFO: Pushing the LDAP configuration to the mongo DB Done [=====================================================================================>---------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 33.33% 0s Push completed successfully! INFO: Working on cluster: cl2 Creating group monitors [========================================================================================================================================================================================================>----------------------------------------] 83.33%INFO: Pushing the hydra_hosts.yml to mongodb INFO: Pushing the LDAP configuration to the mongo DB Done [=====================================================================================>---------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 33.33% 0s Push completed successfully! [root@cdp5007:gauntlet (ad-default)]$ ls -al total 28 drwxr-xr-x. 2 root root 130 Nov 24 09:58 . drwxr--r--. 14 root root 4096 Nov 24 09:56 .. -rw-r--r--. 1 root root 866 Nov 24 09:56 gauntlet_elastic_cl1.yml -rw-r--r--. 1 root root 866 Nov 24 09:56 gauntlet_elastic_cl2.yml -rw-r--r--. 1 root root 6404 Nov 24 09:58 gauntlet_mongo_cl1.yml -rw-r--r--. 1 root root 6404 Nov 24 09:58 gauntlet_mongo_cl2.yml

Modify the gauntlet_elastic_<clustername>.yml file.

vi gauntlet_elastic_<clustername>.yml

Edit the elastic address in the file for multi node setup.

INFO: Working on cluster: cl1 version: 1 elastic_servers: - version: v8 address: "http://<Elastic Server Hostname>:<Elastic Server Port>" basic_auth: true username: "pulse" #EncryptedPassword password: "pPBrVKaoB0QsmCJZNZyYAw==" enable_tls: false client_certificate_path: "" client_key_path: "" client_ca_cert: ""

Modify the elastic address for both clusters.
Push the config to database.

accelo admin database push-config -a

Restart the gauntlet service.

accelo restart ad-gauntlet

Updating MongoDB Cleanup and Compaction Frequency in Hours

By default, when dry run is disabled MongoDB cleanup and compaction will run once a day. To configure the frequency, follow the steps listed below:

Run the following command:

accelo config retention

Answer the prompts. If you’re unsure about how many days you wish to retain, then proceed with the default values.

✔ How many days of data would you like to retain at Mongo DB ?: 15 ✔ How many days of data would you like to retain at Mongo DB for HDFS reports ?: 15 ✔ How many days of data would you like to retain at TSDB ?: 31

When the following prompt comes up, specify the hours of the day during which you would like MongoDB clean up and compaction to run. The value must be a CSV of hours as per the 24 hour time notation.

✔ How often should Mongo DB clean up & compaction run, provide a comma separated string of hours (valid values are [0,23] (Ex. 8,12,15,18)?: 0,6,12,18

Run the following command. When gauntlet runs the next time, MongoDB clean up and compaction will run at the specified hours, once per hour.

accelo admin database push-config

Enabling (TLS) HTTPS for Pulse Web UI Configuration

For details about the configuration, see Enable Native SSL/TLS for Pulse Web UI.

Set Up LDAP for Pulse UI

For details about the configuration, see Set up LDAP for Pulse UI.

Last updated on

Was this page helpful?