Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Follow the below procedure if your client applications are performing S3 multipart uploads that cannot be stopped during the rolling upgrade from Swarm 15.x to Swarm 16.x:
...
Booting the Cluster through CSN
Install the new Swarm rpm and .
select the Swarm 16.x image from the CSN’s UI → Netboot Image.
Add the following at the end of /var/etcopt/caringo/netboot/content/cluster.cfg.
Code Block ec.s3Mode = false
Rolling reboot the cluster into Swarm 16.x.
Once all the nodes are up and running Swarm 16.x, execute this command on the CSN from the dist folder where you’ve installed the support bundle:
Code Block ./swarmctl -d <IP any Swarm node> -C ec.s3Mode -V 1 -p <Swarm admin username>:<password>
...
Remove the following setting from /var/opt/caringo/netboot/content/cluster.cfg.
Code Block ec.s3Mode = false
Booting the Cluster through SCS
Install the new Swarm 16.x image on the SCS and then activate it https://perifery.atlassian.net/wiki/spaces/public/pages/1223491667/SCS+Administration#Upgrading-Swarm-Storage.
Run this command on the SCS:
Code Block scsctl storage config set -d "ec.s3Mode=false"
Rolling reboot the cluster into Swarm 16.x.
Once all the nodes are up and running Swarm 16.x, execute this command on the SCS:
Code Block scsctl storage config set -d "ec.s3Mode=true"