The execution and analytics engines are paired with each other and the data in a given execution engine, for example, execution01, is replicated into the corresponding analytics engine, for example, analytics01. Occasionally the data in the two paired engines get out of sync and need to be re-synced. This is accomplished by "resetting" or clearing out the data in the analytics engine, after which the analytics engine will automatically rebuild itself off of the data in execution.
Run this script when instructed by Appian Support.
|Show usage information
|Password for Admin REST API
Before you run the resetAnalytics script, the application server must be shut down first followed by these engines:
To shut down the engines, use the following script:
./stop.sh -p <password> -s analytics,execution,process-design
This script must be run on every server that contains an analytics engine.
Once you have shut down the engines and the application server, you can run the resetAnalytics script. While running the script, Kafka and Zookeeper must be running.
This script can be used on distributed sites where components are distributed across multiple physical machines. To reset all of the different analytics engines on a distributed site, you must run the script on any of the servers that manage the shard you want reset.
For HA sites, the script must be run on any one of the servers which hosts a copy of the analytics shard(s) being reset.
./resetAnalytics.sh -p <password>
If you only need to reset some, but not all, analytics engines, you can use an optional
-s flag and specify the engines for restart. See the example below.
./resetAnalytics.sh -p <password> -s analytics01,analytics02
Now that you have run the resetAnalytics script, you can restart the following engines:
./services/bin/start.sh -nk -p <password> -s analytics,execution,process-design