Show More
@@ -15,7 +15,7 b' Then upgrade each stack based on instructions provided from the help output:' | |||
|
15 | 15 | |
|
16 | 16 | .. code-block:: bash |
|
17 | 17 | |
|
18 | ./rcstack stack-upgrade | |
|
18 | ./rcstack stack-upgrade <STACK_NAME> | |
|
19 | 19 | |
|
20 | 20 | |
|
21 | 21 | .. note:: |
@@ -24,6 +24,19 b' Then upgrade each stack based on instructions provided from the help output:' | |||
|
24 | 24 | This will spawn 2x more nodes to perform the upgrade and then remove the old instances. This way all incoming traffic |
|
25 | 25 | will be handled continuously without any interruptions on upgrade |
|
26 | 26 | |
|
27 | The above upgrade uses default timeouts to wait for any currently ongoing traffic to stop to kill the workers. | |
|
28 | There are two additional flags that can be used for a faster upgrade that could let to end users errors, or small downtime | |
|
29 | but will enforce the upgrade to be performed as fast as possible. | |
|
30 | ||
|
31 | ||
|
32 | Fast upgrade with max 30s wait time after new upgraded containers start, and wait 5s before force killing old | |
|
33 | containers | |
|
34 | ||
|
35 | ||
|
36 | .. code-block:: bash | |
|
37 | ||
|
38 | ./rcstack stack-upgrade rhodecode --stop-wait 30 --docker-stop-wait 5 | |
|
39 | ||
|
27 | 40 |
|
|
28 | 41 |
|
|
29 | 42 | Install specific version |
General Comments 0
You need to be logged in to leave comments.
Login now