Upgrade a Sharded Cluster to 8.2将分片集群升级到8.2

Disable the Balancer.禁用平衡器。

Connect mongosh to a mongos instance in the sharded cluster, and run sh.stopBalancer() to disable the balancer:将mongosh连接到分片集群中的mongos实例，并运行sh.stopBalancer()以禁用平衡器：

sh.stopBalancer()

sh.getBalancerState()

For more information on disabling the balancer, see Disable the Balancer.有关禁用平衡器的更多信息，请参阅禁用平衡器。

Upgrade the config servers.升级配置服务器。

1. Upgrade the secondary members of the replica set, one at a time.一次升级一个副本集的secondary成员。

   1. Shut down the secondary instance.关闭辅助实例。

      To shut down the mongod process, use mongosh to connect to the cluster member and run the following command:要关闭mongod进程，请使用mongosh连接到集群成员并运行以下命令：

      db.adminCommand( { shutdown: 1 } )

   2. Replace the 8.0 binary with the 8.2 binary.将8.0二进制替换为8.2二进制。

   3. Start the 8.2 binary.启动8.2二进制文件。

      Start the 8.2 binary with the --configsvr, --replSet, and --port. Include any other options as used by the deployment.使用--configsvr、--replSet和--port启动8.2二进制文件。包括部署使用的任何其他选项。

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

      If using a configuration file, update the file to specify sharding.clusterRole: configsvr, replication.replSetName, net.port, and net.bindIp, then start the 8.2 binary:如果使用配置文件，请更新该文件以指定sharding.clusterRole: configsvr、replication.replSetName、net.port和net.bindIp，然后启动8.2二进制文件：

      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.根据部署情况，包括任何其他设置。

   4. Wait for the member to recover to the SECONDARY state before upgrading the next secondary member.在升级下一个辅助成员之前，请等待成员恢复到SECONDARY状态。

      To check the member's state, issue rs.status() in mongosh.要检查成员的状态，请mongosh用发出rs.status()。

2. Step down the replica set primary.逐步关闭primary副本集。

   1. Connect mongosh to the primary and use rs.stepDown() to step down the primary and force an election of a new primary:将mongosh连接到primary，并使用rs.stepDown()退出primary并强制选举新的primary：

      rs.stepDown()

   2. Shut down the stepped-down primary.关闭已降级的小学。

      When rs.status() shows that the primary has stepped down and another member has assumed the PRIMARY state, shut down the stepped-down primary.当rs.status()显示primary服务器已降级，另一个成员已处于PRIMARY状态时，关闭已降级的primary服务器。

      To shut down the stepped-down primary, use mongosh to connect to the primary and run the following command:要关闭已降级的主服务器，请使用mongosh连接到主服务器并运行以下命令：

      db.adminCommand( { shutdown: 1 } )

   3. Replace the mongod binary with the 8.2 binary.将mongod二进制文件替换为8.2二进制文件。

   4. Start the 8.2 binary.启动8.2二进制文件。

      Start the 8.2 with the --configsvr, --replSet, --port, and --bind_ip options. 使用--configsvr、--replSet、--port和--bind_ip选项启动8.2。Include any optional command line options used by the previous deployment:包括以前部署使用的任何可选命令行选项：

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

      If using a configuration file, update the file to specify sharding.clusterRole: configsvr, replication.replSetName, net.port, and net.bindIp, then start the 8.2 binary:如果使用配置文件，请更新该文件以指定sharding.clusterRole: configsvr、replication.replSetName、net.port和net.bindIp，然后启动8.2二进制文件：

      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.包括适合您部署的任何其他配置。

Upgrade the shards.升级分片。

Upgrade the shards one at a time.一次升级一个分片。

For each shard replica set:对于每个分片副本集：

1. Upgrade the secondary members of the replica set, one at a time.一次升级一个副本集的secondary成员。

   1. Shut down the secondary instance.关闭辅助实例。

      To shut down the mongod process, use mongosh to connect to the cluster member and run the following command:要关闭mongod进程，请使用mongosh连接到集群成员并运行以下命令：

      db.adminCommand( { shutdown: 1 } )

   2. Replace the 8.0 binary with the 8.2 binary.将8.0二进制替换为8.2二进制。

      Start the 8.2 binary with the --shardsvr, --replSet, --port, and --bind_ip options. Include any additional command line options as appropriate for your deployment:使用--shardsvr、--replSet、--port和--bind_ip选项启动8.2二进制文件。根据部署情况，包括任何其他命令行选项：

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

      If using a configuration file, update the file to include sharding.clusterRole: shardsvr, replication.replSetName, net.port, and net.bindIp, then start the 8.2 binary:如果使用配置文件，请更新该文件以包含sharding.clusterRole: shardsvr、replication.replSetName、net.port和net.bindIp，然后启动8.2二进制文件：

      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.包括适合您部署的任何其他配置。

   3. Wait for the member to recover to the SECONDARY state before upgrading the next secondary member.在升级下一个辅助成员之前，请等待成员恢复到SECONDARY状态。

      To check the member's state, you can issue rs.status() in mongosh.要检查成员的状态，您可以在mongosh中发出rs.status()。

   4. Repeat for each secondary member.对每个次要成员重复此操作。

2. Step down the replica set primary.逐步关闭primary副本集。

   Connect mongosh to the primary and use rs.stepDown() to step down the primary and force an election of a new primary:将mongosh连接到primary，并使用rs.stepDown()退出primary并强制选举新的primary：

   rs.stepDown()

3. Upgrade the stepped-down primary.升级已降级的primary。

   When rs.status() shows that the primary has stepped down and another member has assumed the PRIMARY state, upgrade the stepped-down primary:当rs.status()显示primary已降级，另一个成员已处于PRIMARY状态时，升级降级的primary：

   1. Shut down the stepped-down primary.关闭已降级的primary。

      To shut down the stepped-down primary, use mongosh to connect to the replica set member and run the following command:要关闭已降级的primary，请使用mongosh连接到副本集成员并运行以下命令：

      db.adminCommand( { shutdown: 1 } )

   2. Replace the mongod binary. with the 8.2 binary.替换mongod二进制文件。使用8.2二进制。

   3. Start the 8.2 binary.启动8.2二进制文件。

      Start the 8.2 binary with the --shardsvr, --replSet, --port, and --bind_ip options. Include any additional command line options as appropriate for your deployment:使用--shardsvr、--replSet、--port和--bind_ip选项启动8.2二进制文件。根据部署情况，包括任何其他命令行选项：

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

      If using a configuration file, update the file to specify sharding.clusterRole: shardsvr, replication.replSetName, net.port, and net.bindIp, then start the 8.2 binary:如果使用配置文件，请更新该文件以指定sharding.clusterRole: shardsvr、replication.replSetName、net.port和net.bindIp，然后启动8.2二进制文件：

      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.包括适合您部署的任何其他配置。

Upgrade the mongos instances.升级mongos实例。

Replace each mongos instance with the 8.2 binary and restart. Include any other configuration as appropriate for your deployment.将每个mongos实例替换为8.2二进制文件并重新启动。包括适合您部署的任何其他配置。

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

Re-enable the balancer.重新启用平衡器。

Using mongosh, connect to a mongos in the cluster and run sh.startBalancer() to re-enable the balancer:使用mongosh，连接到集群中的mongos并运行sh.startBalancer()以重新启用平衡器：

sh.startBalancer()

For more information about re-enabling the balancer, see Enable the Balancer.有关重新启用平衡器的更多信息，请参阅启用平衡器。

Enable backwards-incompatible 8.2 features.启用向后不兼容的8.2功能。

At this point, you can run the 8.2 binaries without the 8.2 features that are incompatible with 8.0.此时，您可以运行8.2二进制文件，而不需要与8.0不兼容的8.2功能。

To enable these 8.2 features, set the feature compatibility version (FCV) to 8.2. You must also set confirm to true if upgrading to 7.0 or later.要启用这些8.2功能，请将功能兼容性版本（FCV）设置为8.2。如果升级到7.0或更高版本，您还必须将confirm设置为true。

On a mongos instance, run the setFeatureCompatibilityVersion command in the admin database:在mongos实例上，在admin数据库中运行setFeatureCompatibilityVersion命令：

db.adminCommand( { setFeatureCompatibilityVersion: "8.2", confirm: true } )

Setting featureCompatibilityVersion (FCV) : "8.2" implicitly performs a replSetReconfig on each shard to add the term field to the shard replica configuration document.设置featureCompatibilityVersion (FCV) : "8.2"隐式地对每个分片执行replSetReconfig，以将term字段添加到分片副本配置文档中。

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 for any reason the command does not complete successfully, you can safely retry the command on the mongos as the operation is idempotent.此命令必须对内部系统集合执行写入操作。如果由于任何原因命令没有成功完成，您可以在mongos上安全地重试该命令，因为该操作是幂等的。

Any orphaned documents that exist on your shards will be cleaned up when you set the setFeatureCompatibilityVersion to 8.2. The cleanup process:当您将setFeatureCompatibilityVersion设置为8.2时，分片上存在的任何孤立文档都将被清理。清理过程：

• Does not block the upgrade from completing, and不会阻止升级完成，以及
• Is rate limited. To mitigate the potential effect on performance during orphaned document cleanup, see Range Deletion Performance Tuning.价格有限。要减轻孤立文档清理过程中对性能的潜在影响，请参阅范围删除性能调整。