##// END OF EJS Templates
fix(stack-upgrade): stack-upgrade will work correctly when no previous containers were running
fix(stack-upgrade): stack-upgrade will work correctly when no previous containers were running

File last commit:

r295:c416f803
r364:f5c46181
Show More
upgrade.rst
55 lines | 1.3 KiB | text/x-rst | RstLexer

Upgrade rcstack

It's usually recommended to start with updating the installer itself by running:

./rcstack self-update

Then upgrade each stack based on instructions provided from the help output:

./rcstack stack-upgrade <STACK_NAME>

Note

./rcstack stack-upgrade rhodecode is a 0 downtime upgrade procedure. This will spawn 2x more nodes to perform the upgrade and then remove the old instances. This way all incoming traffic will be handled continuously without any interruptions on upgrade

The above upgrade uses default timeouts to wait for any currently ongoing traffic to stop to kill the workers. There are two additional flags that can be used for a faster upgrade that could let to end users errors, or small downtime but will enforce the upgrade to be performed as fast as possible.

Fast upgrade with max 30s wait time after new upgraded containers start, and wait 5s before force killing old containers

./rcstack stack-upgrade rhodecode --stop-wait 30 --docker-stop-wait 5

Install specific version

In order to run a specific version of RhodeCode stack simply follow this:

./rcstack cli set-runtime-image 5.0.0
./rcstack stack all down
./rcstack stack all up -d