...
Note that if you are using AWS elasticache service to run Redis Cluster services you can ignore this process and follow the standard upgrade process.
Step 1: wait for all enqueued analyses to end
Step 2: stop kiuwan services
Change the current directory to the old kiuwan-cluster docker scripts and stop all the Kiuwan On-Premises services:
...
This will stop all Kiuwan frontal, analyzer and schedulers containers currently running.
Step
...
3: update your current configuration
In order to update the current Kiuwan On-Premises clients and your volumes global configuration file, you should run the update script located in the new kiuwan-cluster:
| Code Block | ||
|---|---|---|
| ||
cd [INSTALLER_DIR]/docker sudo ./update.sh |
Step
...
4: stop remaining containers and prune
...
Pruning containers is needed to safely upgrade from this version,
*uninstall.sh (version nueva)
Step 4: clean Redis cluster data
*Borrar los datos del redis antiguo (data-local/Redis/data/**).
Step 5: update Redis cluster node information
...
. To do so, run the uninstall.sh script from the new kiuwan-cluster installation directory.
Note that this step will NOT remove any data from your current installation:
| Code Block | ||
|---|---|---|
| ||
cd [INSTALLER_DIR]
sudo ./uninstall.sh |
Step 5: clean Redis cluster data
Redis Cluster current data must be cleaned up in order to start a new fresh cluster. Run the following command:
| Code Block | ||
|---|---|---|
| ||
sudo rm -rf [VOLUMES_DIR]/data-local/Redis/data |
Step 6: update Redis cluster node information
Redis Cluster default configuration has been changed in the following versions of Kiuwan On-Premises. If you are running the provided service you will need to update the Redis Cluster nodes locations.
Edit the global configuration file:
| Code Block | ||
|---|---|---|
| ||
sudo vim [VOLUMES_DIR]/config-shared/globalConfig/globalConfig.properties |
And change these properties values:
| Code Block | ||
|---|---|---|
| ||
redis.cache.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384 |
...
redis.store.nodes=172.17.0.1:6379,172.17.0.1:6380,172.17.0.1:6381,172.17.0.1:6382,172.17.0.1:6383,172.17.0.1:6384 |
If you need to update any other configuration property, you can modify any other configuration option. Changes will be taken into account.
Step
...
8: run the install script for the new version
Running the installation with existing volumes will recreate the new Redis Cluster and start all needed services:
| Code Block | ||
|---|---|---|
| ||
cd [INSTALL_DIR]
sudo ./install.sh |
Step 9
---Si se quiere modificar alguna otra propiedad, este es el momento.
Step 7: install
install.sh (nuevo)
...
: continue with full upgrade steps
You can now continue with the standard upgrade process.