...
...
...
...
Upgrade modes
Upgrade clients
Upgrade full
Upgrade: common steps
Upgrade: common steps
Either you are upgrading only clients or performing a full upgrade, your must follow this steps before continuing.
Step 1: backup your current volumes
Just in case an unexpected error occurs during the upgrade process, it is convenient that your backup all your volumes before proceeding.
Step 2: check clients upgrade bypass configuration
To make sure that your current configuration is not ignoring new available clients, you should check if "kiuwan.clients.update" is set in the following file:
- [VOLUMES_DIR]/config-shared/globalConfig/globalConfig.properties
Locate the key "kiuwan.clients.update" at the end of the file and make sure it is set to true:
Code Block | ||
---|---|---|
| ||
kiuwan.clients.update=true |
When the flag is set to true, all Kiuwan clients will be updated as long as a new version is available.
...
...
...
...
Do not mix up what a Kiuwan On-Premises client version is. These are different concepts:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Step 3: check if you need to follow specific steps for your Kiuwan On-Premises version
Step 4: perform the upgrade
...
...
Specific upgrade notes
This section provides information that you may need to follow in case you are upgrading one of these specific versions (see Checking for updates section if you want to check which version is installed in your company):
Kiuwan On-Premises version | Specific upgrade process needed |
---|---|
2.8.1910.1 | YES |
Upgrading from Kiuwan On-Premises 2.8.1910.1
If you have currently installed Kiuwan On-Premises version 2.8.1910.1, you will need to follow this guide in order to adapt your Kiuwan On-Premises infrastructure to the latest version.
Due to changes in how Redis Cluster is created through the installation process, in order to keep your installation up to date with the latest infrastructure you will need to follow a different approach to perform a full upgrade from this version.
You will need both the kiuwan-cluster version you used to install 2.8.1910.1 and the latest available kiuwan-cluster (that can be downloaded here https://static.kiuwan.com/download/onpremise/kiuwan-cluster.tar.gz). We will refer to this locations:
- [INSTALL_DIR_OLD]: where the old kiuwan-cluster version was untared.
- [INSTALL_DIR]: where the new kiuwan-cluster version has been untared.
Step 1: stop kiuwan services
*stop-kiuwan.sh (version vieja)
Step 2: update your current configuration
*update.sh (version nueva)
Step 3: prune current containers
*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
*Cambiar en el fichero globalConfig.properties las direcciones de los nodos de redis.
...
...
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
Step 6: modify the current configuration if needed
---Si se quiere modificar alguna otra propiedad, este es el momento.
Step 7: install current version
*install.sh (version nueva)
...