Gauntlet Configuration
From Pulse 3.2.0 version, Gauntlet is shipped as a core container known as ad-gauntlet. Also, with the 3.2.0 release, the purge-db and compact-db commands are deprecated. However, you can still use them.
Gauntlet is enabled by default by setting the enable_gauntlet field to true in the accelo.ymlfile. This implies that the configurations for elastic and Mongo snap are generated and pushed to Pulse Mongo DB. ad-gauntlet will then read the configurations from the Mongo DB and snap.
The following configuration in the accelo.yml file enables ad-gauntlet.
config:
enable_gauntlet: true
Retention days for Mongo DB purge can be found in the accelo.yml file.
config:
enable_gauntlet: true
retention:
mongo_retention_days: 15
mongo_hdfs_retention_days: 15
The Retention days can be updated by using the accelo config retention command.
accelo config retention
Optional
If the curator.actions file is changed under $AcceloHome/config/logsearch directory then execute the following command to generate the config for the gauntlet. The files will be created under $AcceloHome/config/gauntlet directory.
accelo migrate gauntlet
Once the accelo.yml file is updated, you must push it to Mongo DB executing the following command.
accelo admin database push-config
The above command generates and pushes the new config files for Mongo gauntlet snap and elastic gauntlet snap using the retention days mentioned in the accelo.yml file to Mongo DB.
By default, the files generated are not saved locally. Running the above command with the -s flag will save the files locally in the $AcceloHome/config/gauntlet directory.
accelo admin database push-config -s
Disable Dry Run
By default, the ad-gauntlet container will run all the snaps in dry run mode. It does not delete or purge any data but prints the deleted/purged data to the stdout as it does. You can verify this behavior that it’s printing things as desired.
Execute the following command to generate the ad-core.yml file if it does not exist at the $AcceloHome/config/docker/ad-core/yml directory.
accelo admin makeconfig ad-core
Update the DRY_RUN environment variable and set it to false to disable dry run mode.
ad-gauntlet:
image: ad-gauntlet
container_name: ad-gauntlet
environment:
- DRY_RUN_ENABLE=false # Update this environment variable
Restart the ad-gauntlet container by executing the following command, to apply the changes.
accelo restart ad-gauntlet
Disable Gauntlet
Update the accelo.yml file, set enable_gauntlet: false and push the file to Mongo DB using the following command.
accelo admin database push-config
The above command deletes all the gauntlet configurations from the Mongo DB. This results in ad-gauntlet not snapping the data.
Run ad-logsearch-curator
Once the gauntlet is disabled, the curator can be brought up by redeploying the logsearch addon.
Unselect LogSearch and press the enter key
accelo deploy addons
INFO: Active Cluster: adodp
? Select the components you would like to install: [Use arrows to move, enter to select, type to filter]
[ ] Kafka 0.10.2 Connector
[ ] Kafka Connector
[ ] LDAP
> [ ] LogSearch
[ ] Notifications
[ ] Oozie Connector
[ ] Proxy
Select LogSearch and press the enter key.
accelo deploy addons
INFO: Active Cluster: adodp
? Select the components you would like to install: [Use arrows to move, enter to select, type to filter]
[ ] Kafka 0.10.2 Connector
[ ] Kafka Connector
[ ] LDAP
> [x] LogSearch
[ ] Notifications
[ ] Oozie Connector
[ ] Proxy