Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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.

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

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

    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:

    ./swarmctl -d <IP any Swarm node> -C ec.s3Mode -V 1 -p <Swarm admin username>:<password>

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:

    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:

    scsctl storage config set -d "ec.s3Mode=true"
  • No labels