Update an existing Warp 10 deployment
Warp 10 is designed to avoid breaking changes. Any new configuration has a default value.
- Input signatures of WarpScript functions that were accepted by a previous release are still compatible.
- In a production environment, we strongly suggest you to have a preproduction standalone version to test your existing WarpScript unit tests.
Steps below describes a basic update. Sometimes,
warp10-standalone.sh may evolve too: please read UPDATE.md to check if there are additional steps needed for the new revision.
Step 1. Download latest Warp 10 release
Go to download page, download the latest tar.gz. Store the new version number in a shell variable for later:
Step 2. Extract the tar.gz to a temporary directory.
mkdir -p /tmp/warp10new tar xf warp10-$NEWVERSION.tar.gz -C /tmp/warp10new
Step 3. Upgrade jar and launch script
Copy the new jar to bin directory, backup old files if any problem, and change the WARP10_REVISION.
sudo cp /opt/warp10/bin/warp10-standalone.sh /opt/warp10/bin/warp10-standalone.sh.backup sudo cp /tmp/warp10new/warp10-$NEWVERSION/bin/warp10-$NEWVERSION.jar /opt/warp10/bin sudo sed -i "s/^WARP10_REVISION=.*/WARP10_REVISION=$NEWVERSION/g" /opt/warp10/bin/warp10-standalone.sh
Step 4. Restart Warp 10, looking at the logs file.
In a new terminal, follow the Warp 10 logs:
sudo tail -f /opt/warp10/logs/warp10.log
In another terminal, restart Warp 10.
If you did set up a systemd unit:
sudo systemctl restart warp10.service
If you didn't:
sudo /opt/warp10/bin/warp10-standalone.init restart
The logs will tell you if there is a new configuration missing. Contact us if any trouble.
On a distributed cluster, you can update and restart node by node to avoid service interruption.