Mongos

  • Canonical
Channel Revision Published Runs on
latest/candidate 24 04 Oct 2024
Ubuntu 22.04
latest/beta 24 04 Oct 2024
Ubuntu 22.04
6/stable 24 08 Oct 2024
Ubuntu 22.04
6/beta 10 26 Mar 2024
Ubuntu 22.04
6/edge 30 12 Nov 2024
Ubuntu 22.04
juju deploy mongos --channel 6/edge
Show information

Platform:

Ubuntu
22.04

Perform a minor upgrade on a mongos router

This page contains:

To perform an upgrade on a MongoDB K8s sharded cluster, see the Charmed MongoDB documentation.


Supported revisions

Below is a list of revisions of Charmed MongoDB that support upgrades.

:warning: Only upgrade to or from these supported revisions in a production environment.

Minor upgrade steps

Here is a summary of the steps to perform a minor upgrade.:

  1. Determine your current revision
  2. Determine new revision
  3. Upgrade the router

Step 1: Determine your current revision

Find determine your current revision:

juju status | grep <juju-app-name> | head -1 | awk '{print $5}'

If your current revision is not in the list, then upgrade is not supported.

In the case that your upgrade is not successful, you will need this revision number to roll back your application.

Step 2: Determine new revision

Choose a revision to upgrade to from the list of available revisions to upgrade to

Step 3: Upgrade the router

Using the revision from Step 2, upgrade your application

juju refresh mongos --revision=<revision number>

The upgrade should begin, and upgrade all deployed mongos routers. You can watch and wait for the upgrade to succeed with juju status --watch 1s.

If all units show active and idle statuses after upgrading, then your upgrade succeeded.

If your upgrade failed, then juju status will show that the unit is blocked with the message Unhealthy after refresh. You can do the following:

  1. Recommended: Wait for 5-10 minutes to see if the router can heal itself
  2. Recommended: Roll back. To roll back complete redo Step 3 using the revision number from Step 1.
  3. Not Recommended: Force an upgrade by running juju run mongos/leader force-refresh-start. Please note this can break your database and is not recommended.