> This page location: /docs.md > /docs/development.md > /docs/manual/release-notes.md > /docs/manual/release-notes/9.0.md > /docs/manual/release-notes/9.0-upgrade.md

> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Upgrade 8.3 Sharded Cluster to 9.0

Familiarize yourself with the content of this document, including thoroughly reviewing the prerequisites, before upgrading to MongoDB 9.0.

The following steps outline the procedure to upgrade a [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) that is a shard member from version 8.3 to 9.0.

If you need guidance on upgrading to 9.0, [MongoDB professional services](https://www.mongodb.com/products/consulting/) offer major version upgrade support to help ensure a smooth transition without interruption to your MongoDB application.

## Upgrade Recommendations and Checklists

When upgrading, consider the following:

### Upgrade Version Path

To upgrade an existing MongoDB deployment to 9.0, you must be running a 8.3 or 8.0 release.

To upgrade from a version earlier than the 8.0-series, you must successively upgrade major releases until you have upgraded to 8.0-series. For example, if you are running a 7.0-series, you must [upgrade first to 8.0](https://www.mongodb.com/docs/manual/release-notes/8.0.md#std-label-8.0-upgrade) *before* you can upgrade to 9.0.

### Check Driver Compatibility

Before you upgrade MongoDB, check that you're using a MongoDB 9.0-compatible driver. Consult the [driver documentation](https://www.mongodb.com/docs/drivers/) for your specific driver to verify compatibility with MongoDB 9.0.

Upgraded deployments that run on incompatible drivers might encounter unexpected or undefined behavior.

### Preparedness

Before beginning your upgrade, see the [Compatibility Changes in MongoDB 9.0](https://www.mongodb.com/docs/manual/release-notes/9.0-compatibility.md#std-label-9.0-compatibility) document to ensure that your applications and deployments are compatible with MongoDB 9.0. Resolve the incompatibilities in your deployment before starting the upgrade.

Before upgrading MongoDB, always test your application in a staging environment before deploying the upgrade to your production environment.

### Downgrade Consideration

Starting in MongoDB 8.3, you can downgrade your MongoDB version to the immediately previous minor or major version.

MongoDB only supports single-version downgrades. You cannot downgrade to a release that is multiple versions behind your current release.

For example, you can downgrade a 9.0-series to a 8.0-series deployment. However, further downgrading that 8.0-series deployment to a 7.0-series deployment is not supported.

To learn more, see [Downgrade 9.0 to 8.3.](https://www.mongodb.com/docs/manual/release-notes/9.0-downgrade.md#std-label-9.0-downgrade)

## Prerequisites

### All Members Version

To upgrade a sharded cluster to 9.0, **all** members of the cluster must run version 8.3 or 8.0. The upgrade process checks all components of the cluster and produces warnings if any component is running a version earlier than 8.0. To upgrade a sharded cluster from 8.0, see [Upgrade 8.0 to 9.0 Sharded Cluster](https://www.mongodb.com/docs/manual/release-notes/9.0-upgrade-from-8.0-sharded-cluster.md#std-label-9.0-upgrade-from-8.0-sharded-cluster). To upgrade a sharded cluster from 7.0-series and earlier, *first* [upgrade all members of the sharded cluster to the latest 8.0-series release](https://www.mongodb.com/docs/manual/release-notes/8.0-upgrade-sharded-cluster.md#std-label-8.0-upgrade-sharded-cluster), and then follow the procedure to upgrade from MongoDB 8.3 to 9.0.

### Feature Compatibility Version

The 8.3 sharded cluster must have `featureCompatibilityVersion` set to 8.3.

To ensure that all members of the sharded cluster have `featureCompatibilityVersion` set to 8.3, connect to each shard replica set member and each config server replica set member. Then, check the `featureCompatibilityVersion`:

**Tip:**

For a sharded cluster that has access control enabled, to run the following command against a shard replica set member, you must connect to the member as a [shard local user.](https://www.mongodb.com/docs/manual/core/security-users.md#std-label-shard-local-users)

```javascript
db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )
```

**Output:**

```json
"featureCompatibilityVersion" : { "version" : "8.3" }
```

To set or update `featureCompatibilityVersion`, run the following command on the [`mongos`:](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos)

```javascript
db.adminCommand( { setFeatureCompatibilityVersion: "8.3", confirm: true } )
```

For more information, see [`setFeatureCompatibilityVersion`.](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#mongodb-dbcommand-dbcmd.setFeatureCompatibilityVersion)

### Replica Set Member State

For shards and config servers, ensure that no replica set member is in the [`ROLLBACK`](https://www.mongodb.com/docs/manual/reference/replica-states.md#mongodb-replstate-replstate.ROLLBACK) or [`RECOVERING`](https://www.mongodb.com/docs/manual/reference/replica-states.md#mongodb-replstate-replstate.RECOVERING) state.

```javascript
db.adminCommand( { replSetGetStatus: 1 } )
```

### Back up the `config` Database

*Optional but Recommended.* As a precaution, create a backup of the `config` database *before* upgrading the sharded cluster.

## Download 9.0 Binaries

### Use a Package Manager

If you installed MongoDB from the MongoDB `apt`, `yum`, `dnf`, or `zypper` repositories, you should upgrade to 9.0 using your package manager.

Follow the appropriate [9.0 installation instructions](https://www.mongodb.com/docs/manual/installation.md#std-label-tutorial-installation) for your Linux system. This requires adding a repository for the new release, then performing the actual upgrade process.

### Download 9.0 Binaries Manually

If you have not installed MongoDB using a package manager, you can manually download the MongoDB binaries from the [MongoDB Download Center](https://www.mongodb.com/try/download/).

See [9.0 installation instructions](https://www.mongodb.com/docs/manual/installation.md#std-label-tutorial-installation) for more information.

## Upgrade Procedure

1. Disable the balancer

   Connect [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to a [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) instance in the sharded cluster, and run [`sh.stopBalancer()`](https://www.mongodb.com/docs/manual/reference/method/sh.stopbalancer.md#mongodb-method-sh.stopBalancer) to disable the balancer:

   ```javascript
   sh.stopBalancer()
   ```

   **Note:**

   If a migration is in progress, the system completes the in-progress migration before stopping the balancer. You can run [`sh.isBalancerRunning()`](https://www.mongodb.com/docs/manual/reference/method/sh.isbalancerrunning.md#mongodb-method-sh.isBalancerRunning) to check the balancer's current state.

   To verify that the balancer is disabled, run [`sh.getBalancerState()`](https://www.mongodb.com/docs/manual/reference/method/sh.getbalancerstate.md#mongodb-method-sh.getBalancerState), which returns `false` if the balancer is disabled:

   ```javascript
   sh.getBalancerState()
   ```

   For more information on disabling the balancer, see [Disable the Balancer.](https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer.md#std-label-sharding-balancing-disable-temporarily)

2. Upgrade the config servers

   Upgrade the [secondary](https://www.mongodb.com/docs/manual/core/replica-set-members.md#std-label-replica-set-secondary-members) members of the replica set, one at a time.

   Shut down the secondary instance.

   To shut down the [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) process, use [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to connect to the cluster member and run the following command:

   ```javascript
   db.adminCommand( { shutdown: 1 } )
   ```

   Replace the 8.3 binary with the 9.0 binary.

   Start the 9.0 binary.

   Start the 9.0 binary with the [`--configsvr`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--configsvr), [`--replSet`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--replSet), and [`--port`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--port). Include any other options as used by the deployment.

   ```bash
   mongod --configsvr --replSet <replSetName> --port <port> --dbpath <path> --bind_ip localhost,<ip address>
   ```

   If you use a [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options.md#std-label-configuration-options), update the file to specify [`sharding.clusterRole: configsvr`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-sharding.clusterRole), [`replication.replSetName`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-replication.replSetName), [`net.port`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.port), and [`net.bindIp`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.bindIp), then start the 9.0 binary:

   ```yaml
   sharding:
      clusterRole: configsvr
   replication:
      replSetName: <string>
   net:
      port: <port>
      bindIp: localhost,<ip address>
   storage:
      dbpath: <path>
   ```

   Include any other settings as appropriate for your deployment.

   Wait for the member to recover to the `SECONDARY` state before upgrading the next secondary member.

   To check the member's state, issue [`rs.status()`](https://www.mongodb.com/docs/manual/reference/method/rs.status.md#mongodb-method-rs.status) in [`mongosh`.](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh)

   Repeat for each secondary member.

   Step down the replica set primary.

   Connect [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to the primary and use [`rs.stepDown()`](https://www.mongodb.com/docs/manual/reference/method/rs.stepdown.md#mongodb-method-rs.stepDown) to step down the primary and force an election of a new primary:

   ```javascript
   rs.stepDown()
   ```

   Shut down the stepped-down primary.

   When [`rs.status()`](https://www.mongodb.com/docs/manual/reference/method/rs.status.md#mongodb-method-rs.status) shows that the primary has stepped down and another member has assumed the `PRIMARY` state, shut down the stepped-down primary.

   To shut down the stepped-down primary, use [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to connect to the primary and run the following command:

   ```javascript
   db.adminCommand( { shutdown: 1 } )
   ```

   Replace the [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) binary with the 9.0 binary.

   Start the 9.0 binary.

   Start the 9.0 with the [`--configsvr`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--configsvr), [`--replSet`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--replSet), [`--port`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--port), and [`--bind_ip`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--bind_ip) options. Include any optional command line options used by the previous deployment:

   ```bash
   mongod --configsvr --replSet <replSetName> --port <port> --dbpath <path> --bind_ip localhost,<ip address>
   ```

   If using a [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options.md#std-label-configuration-options), update the file to specify [`sharding.clusterRole: configsvr`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-sharding.clusterRole), [`replication.replSetName`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-replication.replSetName), [`net.port`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.port), and [`net.bindIp`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.bindIp), then start the 9.0 binary:

   ```yaml
   sharding:
      clusterRole: configsvr
   replication:
      replSetName: <string>
   net:
      port: <port>
      bindIp: localhost,<ip address>
   storage:
      dbpath: <path>
   ```

   Include any other configuration as appropriate for your deployment.

3. Upgrade the shards

   Upgrade the shards one at a time.

   For each shard replica set:

   Upgrade the [secondary](https://www.mongodb.com/docs/manual/core/replica-set-members.md#std-label-replica-set-secondary-members) members of the replica set, one at a time.

   Shut down the secondary instance.

   To shut down the [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) process, use [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to connect to the cluster member and run the following command:

   ```javascript
   db.adminCommand( { shutdown: 1 } )
   ```

   Replace the 8.3 binary with the 9.0 binary.

   Start the 9.0 binary with the [`--shardsvr`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--shardsvr), [`--replSet`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--replSet), [`--port`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--port), and [`--bind_ip`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--bind_ip) options. Include any additional command line options as appropriate for your deployment:

   ```bash
   mongod --shardsvr --replSet <replSetName> --port <port> --dbpath <path> --bind_ip localhost,<ip address>
   ```

   If using a [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options.md#std-label-configuration-options), update the file to include [`sharding.clusterRole: shardsvr`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-sharding.clusterRole), [`replication.replSetName`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-replication.replSetName), [`net.port`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.port), and [`net.bindIp`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.bindIp), then start the 9.0 binary:

   ```yaml
   sharding:
      clusterRole: shardsvr
   replication:
      replSetName: <string>
   net:
      port: <port>
      bindIp: localhost,<ip address>
   storage:
      dbpath: <path>
   ```

   Include any other configuration as appropriate for your deployment.

   Wait for the member to recover to the `SECONDARY` state before upgrading the next secondary member.

   To check the member's state, you can issue [`rs.status()`](https://www.mongodb.com/docs/manual/reference/method/rs.status.md#mongodb-method-rs.status) in [`mongosh`.](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh)

   Repeat for each secondary member.

   Step down the replica set primary.

   Connect [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to the primary and use [`rs.stepDown()`](https://www.mongodb.com/docs/manual/reference/method/rs.stepdown.md#mongodb-method-rs.stepDown) to step down the primary and force an election of a new primary:

   ```javascript
   rs.stepDown()
   ```

   Upgrade the stepped-down primary.

   When [`rs.status()`](https://www.mongodb.com/docs/manual/reference/method/rs.status.md#mongodb-method-rs.status) shows that the primary has stepped down and another member has assumed the `PRIMARY` state, upgrade the stepped-down primary:

   Shut down the stepped-down primary.

   To shut down the stepped-down primary, use [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh) to connect to the replica set member and run the following command:

   ```javascript
   db.adminCommand( { shutdown: 1 } )
   ```

   Replace the [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) binary with the 9.0 binary.

   Start the 9.0 binary.

   Start the 9.0 binary with the [`--shardsvr`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--shardsvr), [`--replSet`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--replSet), [`--port`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--port), and [`--bind_ip`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--bind_ip) options. Include any additional command line options as appropriate for your deployment:

   ```bash
   mongod --shardsvr --replSet <replSetName> --port <port> --dbpath <path> --bind_ip localhost,<ip address>
   ```

   If using a [configuration file](https://www.mongodb.com/docs/manual/reference/configuration-options.md#std-label-configuration-options), update the file to specify [`sharding.clusterRole: shardsvr`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-sharding.clusterRole), [`replication.replSetName`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-replication.replSetName), [`net.port`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.port), and [`net.bindIp`](https://www.mongodb.com/docs/manual/reference/configuration-options.md#mongodb-setting-net.bindIp), then start the 9.0 binary:

   ```yaml
   sharding:
         clusterRole: shardsvr
   replication:
      replSetName: <string>
   net:
      port: <port>
      bindIp: localhost,<ip address>
   storage:
      dbpath: <path>
   ```

   Include any other configuration as appropriate for your deployment.

4. Upgrade the `mongos` instances

   **Important:**

   Upgrade all config server replica set (CSRS) instances first, followed by all shard members and, finally, the `mongos` instances. Upgrading `mongos` before completing these upgrades can result in compatibility issues.

   Replace each [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) instance with the 9.0 binary and restart. Include any other configuration as appropriate for your deployment.

   **Note:**

   The [`--bind_ip`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#std-option-mongod.--bind_ip) option must be specified when the sharded cluster members are run on different hosts or if remote clients connect to the sharded cluster.

   ```bash
   mongos --configdb csReplSet/<rsconfigsver1:port1>,<rsconfigsver2:port2>,<rsconfigsver3:port3> --bind_ip localhost,<ip address>
   ```

5. Re-enable the balancer

   Using [`mongosh`](https://www.mongodb.com/docs/mongodb-shell.md#mongodb-binary-bin.mongosh), connect to a [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) in the cluster and run [`sh.startBalancer()`](https://www.mongodb.com/docs/manual/reference/method/sh.startbalancer.md#mongodb-method-sh.startBalancer) to re-enable the balancer:

   ```javascript
   sh.startBalancer()
   ```

   For more information about re-enabling the balancer, see [Enable the Balancer.](https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer.md#std-label-sharding-balancing-enable)

6. Enable backwards-incompatible 9.0 features

   At this point, you can run the 9.0 binaries without the 9.0 [features](https://www.mongodb.com/docs/manual/release-notes/9.0-compatibility.md#std-label-9.0-downgrade-incompatible) that are incompatible with 8.3.

   To enable these 9.0 features, set the feature compatibility version (`FCV`) to 9.0. You must also set `confirm` to true.

   **Tip:**

   Enabling these backwards-incompatible features can complicate the downgrade process since you must remove any persisted backwards-incompatible features before you downgrade.

   It is recommended that after upgrading, you allow your deployment to run without enabling these features for a burn-in period to ensure the likelihood of downgrade is minimal. When you are confident that the likelihood of downgrade is minimal, enable these features.

   On a [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) instance, run the [`setFeatureCompatibilityVersion`](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#mongodb-dbcommand-dbcmd.setFeatureCompatibilityVersion) command in the `admin` database:

   ```javascript
   db.adminCommand( { setFeatureCompatibilityVersion: "9.0", confirm: true } )
   ```

   Setting [featureCompatibilityVersion (FCV) : "9.0"](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#std-label-set-fcv) implicitly performs a [`replSetReconfig`](https://www.mongodb.com/docs/manual/reference/command/replsetreconfig.md#mongodb-dbcommand-dbcmd.replSetReconfig) on each shard to add the [`term`](https://www.mongodb.com/docs/manual/reference/replica-configuration.md#mongodb-rsconf-rsconf.term) field to the shard replica configuration document.

   The command doesn't complete until the new configuration propagates to a majority of replica set members.

   This command must perform writes to an internal system collection. If the command does not complete, you can safely retry the command on the [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) as the operation is idempotent.

   **Note:**

   When you upgrade the FCV (feature compatibility version) to 9.0, MongoDB migrates metadata from the config server to the shards. This one time migration can make the upgrade take longer on clusters with many databases, collections, or chunks.

   While metadata for a database or tracked collection is being cloned, operations that modify, rename, reshard, or drop that database or collection must wait until cloning completes.

   **Note:**

   When you upgrade the FCV (feature compatibility version) to 9.0, MongoDB moves metadata from the config server to the shards. During this transition, the FCV (feature compatibility version) upgrade drains and blocks chunk operations, including:

   - [`split`](https://www.mongodb.com/docs/manual/reference/command/split.md#mongodb-dbcommand-dbcmd.split)

   - [`mergeChunks`](https://www.mongodb.com/docs/manual/reference/command/mergechunks.md#mongodb-dbcommand-dbcmd.mergeChunks)

   - [`mergeAllChunksOnShard`](https://www.mongodb.com/docs/manual/reference/command/mergeallchunksonshard.md#mongodb-dbcommand-dbcmd.mergeAllChunksOnShard)

   - Migrations, manual and balancer-issued

   Chunk operations resume after the FCV (feature compatibility version) upgrade completes.

   **Note:**

   When you upgrade the FCV (feature compatibility version) to 9.0, MongoDB moves collection metadata from the config server to the shards. While the FCV (feature compatibility version) upgrade clones this metadata, [`movePrimary`](https://www.mongodb.com/docs/manual/reference/command/moveprimary.md#mongodb-dbcommand-dbcmd.movePrimary) blocks and fails with `ConflictingOperationInProgress`.

   Retry [`movePrimary`](https://www.mongodb.com/docs/manual/reference/command/moveprimary.md#mongodb-dbcommand-dbcmd.movePrimary) after the FCV (feature compatibility version) upgrade completes.

   **Warning: mongos FCV Compatibility**

   The [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) binary cannot connect to [`mongod`](https://www.mongodb.com/docs/manual/reference/program/mongod.md#mongodb-binary-bin.mongod) instances whose [feature compatibility version (FCV)](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#std-label-view-fcv) is greater than that of the [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos). For example, you cannot connect a MongoDB 8.3 version [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) to a 9.0 sharded cluster with [FCV](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#std-label-view-fcv) set to 9.0. You can, however, connect a MongoDB 8.3 version [`mongos`](https://www.mongodb.com/docs/manual/reference/program/mongos.md#mongodb-binary-bin.mongos) to a 9.0 sharded cluster with [FCV](https://www.mongodb.com/docs/manual/reference/command/setfeaturecompatibilityversion.md#std-label-view-fcv) set to 8.3.

## Troubleshooting

If you experience startup issues after you upgrade, contact [MongoDB Support](https://support.mongodb.com/welcome) for assistance.

## Additional Upgrade Procedures

- To upgrade a standalone, see [Upgrade 8.3 Standalone to 9.0.](https://www.mongodb.com/docs/manual/release-notes/9.0-upgrade-standalone.md#std-label-9.0-upgrade-standalone)

- To upgrade a replica set, see [Upgrade 8.3 Replica Set to 9.0.](https://www.mongodb.com/docs/manual/release-notes/9.0-upgrade-replica-set.md#std-label-9.0-upgrade-replica-set)
