Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel1
maxLevel2
outlinefalse
typelist
printablefalse

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

  1. Install the new Swarm rpm and .

  2. select the Swarm 16.x image from the CSN’s UI → Netboot Image.

  3. Add the following at the end of /var/etcopt/caringo/netboot/content/cluster.cfg.

    Code Block
    ec.s3Mode = false
  4. Rolling reboot the cluster into Swarm 16.x.

  5. 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>

...

  1. Remove the following setting from /var/opt/caringo/netboot/content/cluster.cfg.

    Code Block
    ec.s3Mode = false

Booting the Cluster through SCS

  1. 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.

  2. Run this command on the SCS:

    Code Block
    scsctl storage config set -d "ec.s3Mode=false"
  3. Rolling reboot the cluster into Swarm 16.x.

  4. 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"