部署地理位置冗余的自管理副本集

使用适当的选项启动副本集的每个成员。

为每个成员启动一个 mongod实例，设置如下：

• 将 replication.replSetName 选项设置为副本集名称。如果您的应用程序连接到多个副本集，则每个副本集的名称必须不同。

• 将 net.bindIp 选项设置为主机名/IP，或使用逗号隔开的主机名/IP 列表。

• 设置适合您的部署的任何其他设置。

在本教程中，三个 mongod 实例与以下主机相关联：

以下示例通过 --replSet 和 --bind_ip 命令行选项指定副本集名称和 IP 绑定：

mongod --replSet "rs0" --bind_ip localhost,<hostname(s)|ip address(es)>

对于 <hostname(s)|ip address(es)>，指定您的 mongod 实例的主机名和/或 IP 地址，远程客户端（包括副本集的其他成员）可以使用它们连接到该实例。

或者，您也可以在配置文件中指定 replica set name 和 ip addresses：

replication:
   replSetName: "rs0"
net:
   bindIp: localhost,<hostname(s)|ip address(es)>

要使用配置文件启动 mongod，请使用 --config 选项指定配置文件的路径：

mongod --config <path-to-config>

在生产部署中，您可以配置一个初始化脚本来管理此进程。初始化脚本超出了本文档的范围。

将 mongosh 连接到其中一个 mongod 实例。

在运行 mongod 的同一台机器上（本教程中为 mongodb0.example.net）启动 mongosh。要连接到在默认端口 27017 上监听本地主机的 mongod，只需发出以下命令：

mongosh

您可能需要指定 mongosh 二进制文件的路径，具体取决于您的路径。

如果 mongod 未在默认端口上运行，请为 mongosh 指定 --port 选项。

启动新副本集。

通过 mongosh，在副本集成员 0 上运行 rs.initiate()。

rs.initiate( {
   _id : "rs0",
   members: [
      { _id: 0, host: "mongodb0.example.net:27017" },
      { _id: 1, host: "mongodb1.example.net:27017" },
      { _id: 2, host: "mongodb2.example.net:27017" }
   ]
})

MongoDB 使用默认副本集配置启动副本集。

查看副本集配置。

使用 rs.conf() 显示副本集配置对象：

rs.conf()

副本集配置对象与以下内容类似：

{
   "_id" : "rs0",
   "version" : 1,
   "protocolVersion" : NumberLong(1),
   "members" : [
      {
         "_id" : 0,
         "host" : "mongodb0.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 1,
         "host" : "mongodb1.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 2,
         "host" : "mongodb2.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      }
      
   ],
   "settings" : {
      "chainingAllowed" : true,
      "heartbeatIntervalMillis" : 2000,
      "heartbeatTimeoutSecs" : 10,
      "electionTimeoutMillis" : 10000,
      "catchUpTimeoutMillis" : -1,
      "getLastErrorModes" : {
      },
      "getLastErrorDefaults" : {
         "w" : 1,
         "wtimeout" : 0
      },
      "replicaSetId" : ObjectId("585ab9df685f726db2c6a840")
   }
}

Optional. Configure the member eligibility for becoming primary.

某些情况下，您可能希望一个数据中心内的节点先于其他数据中心内的节点被选为主节点。您可以修改节点的 priority，使一个数据中心中的节点的 priority 高于其他数据中心的节点。

Some members of the replica set, such as members that have networking restraint or limited resources, should not be able to become primary in a 故障切换. Configure members that should not become primary to have priority 0.

For example, to lower the relative eligibility of the member located in one of the sites (in this example, mongodb2.example.net), set the member's priority to 0.5.

1. View the replica set configuration to determine the members array position for the member.

   注意

   The array position is not the same as the _id.

   rs.conf()

2. Copy the replica set configuration object to a variable (to cfg in the example below). Then, in the variable, set the correct priority for the member. Pass the variable to rs.reconfig() to update the replica set configuration.

   For example, to set priority for the third member in the array (i.e., the member at position 2), issue the following sequence of commands:

   cfg = rs.conf()
   cfg.members[2].priority = 0.5
   rs.reconfig(cfg)

   注意

   The rs.reconfig() shell method can force the current primary to step down, causing an election. When the primary steps down, all clients disconnect. This is the intended behavior. While median time to elect a new primary should not typically exceed 12 seconds, make sure any replica configuration changes occur during scheduled maintenance periods.

After these commands return, you have a geographically redundant three-member replica set.

确保副本集有一个主节点。

使用 rs.status() 标识副本集中的主节点。

使用适当的选项启动副本集的每个成员。

为每个成员启动一个 mongod实例，设置如下：

• 集 replication.replSetName option to the replica set name,

  如果您的应用程序连接到多个副本集，则每个副本集的名称必须不同。有些驱动程序会按副本集名称对副本集连接进行分组。

• 集 net.bindIp option to the hostname/ip address or a comma-delimited list of hostnames/ip addresses, and

• 设置适合您的部署的任何其他设置。

In this tutorial, the five mongod instances are associated with the following hosts:

以下示例通过 --replSet 和 --bind_ip 命令行选项指定副本集名称和 IP 绑定：

mongod --replSet "rs0" --bind_ip localhost,<hostname(s)|ip address(es)>

对于 <hostname(s)|ip address(es)>，指定您的 mongod 实例的主机名和/或 IP 地址，远程客户端（包括副本集的其他成员）可以使用它们连接到该实例。

Alternatively, you can also specify the replica set name and the hostnames/ip addresses in a 配置文件:

replication:
   replSetName: "rs0"
net:
   bindIp: localhost,<hostname(s)|ip address(es)>

要使用配置文件启动 mongod，请使用 --config 选项指定配置文件的路径：

mongod --config <path-to-config>

在生产部署中，您可以配置一个初始化脚本来管理此进程。初始化脚本超出了本文档的范围。

将 mongosh 连接到其中一个 mongod 实例。

在运行 mongod 的同一台机器上（本教程中为 mongodb0.example.net）启动 mongosh。要连接到在默认端口 27017 上监听本地主机的 mongod，只需发出以下命令：

mongosh

您可能需要指定 mongosh 二进制文件的路径，具体取决于您的路径。

如果 mongod 未在默认端口上运行，请为 mongosh 指定 --port 选项。

启动新副本集。

通过 mongosh，在副本集成员 0 上运行 rs.initiate()。

rs.initiate( {
   _id : "rs0",
   members: [
      { _id: 0, host: "mongodb0.example.net:27017" },
      { _id: 1, host: "mongodb1.example.net:27017" },
      { _id: 2, host: "mongodb2.example.net:27017" },
      { _id: 3, host: "mongodb3.example.net:27017" },
      { _id: 4, host: "mongodb4.example.net:27017" }
   ]
})

查看副本集配置。

使用 rs.conf() 显示副本集配置对象：

rs.conf()

副本集配置对象与以下内容类似：

{
   "_id" : "rs0",
   "version" : 1,
   "protocolVersion" : NumberLong(1),
   "writeConcernMajorityJournalDefault" : true,
   "members" : [
      {
         "_id" : 0,
         "host" : "mongodb0.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 1,
         "host" : "mongodb1.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 2,
         "host" : "mongodb2.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 3,
         "host" : "mongodb3.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      },
      {
         "_id" : 4,
         "host" : "mongodb4.example.net:27017",
         "arbiterOnly" : false,
         "buildIndexes" : true,
         "hidden" : false,
         "priority" : 1,
         "tags" : {
         },
         "secondaryDelaySecs" : NumberLong(0),
         "votes" : 1
      }
   ],
   "settings" : {
      "chainingAllowed" : true,
      "heartbeatIntervalMillis" : 2000,
      "heartbeatTimeoutSecs" : 10,
      "electionTimeoutMillis" : 10000,
      "catchUpTimeoutMillis" : -1,
      "catchUpTakeoverDelayMillis" : 30000,
      "getLastErrorModes" : {
      },
      "getLastErrorDefaults" : {
         "w" : 1,
         "wtimeout" : 0
      },
      "replicaSetId" : ObjectId("5df2c9ccc21c478b838b98d6")
   }
}

Optional. Configure the member eligibility for becoming primary.

某些情况下，您可能希望一个数据中心内的节点先于其他数据中心内的节点被选为主节点。您可以修改节点的 priority，使一个数据中心中的节点的 priority 高于其他数据中心的节点。

Some members of the replica set, such as members that have networking restraint or limited resources, should not be able to become primary in a 故障切换. Configure members that should not become primary to have priority 0.

For example, to lower the relative eligibility of the member located in one of the sites (in this example, mongodb2.example.net), set the member's priority to 0.5.

1. View the replica set configuration to determine the members array position for the member.

   注意

   The array position is not the same as the _id.

   rs.conf()

2. Copy the replica set configuration object to a variable (to cfg in the example below). Then, in the variable, set the correct priority for the member. Pass the variable to rs.reconfig() to update the replica set configuration.

   For example, to set priority for the third member in the array (i.e., the member at position 2), issue the following sequence of commands:

   cfg = rs.conf()
   cfg.members[2].priority = 0.5
   rs.reconfig(cfg)

   注意

   The rs.reconfig() shell method can force the current primary to step down, causing an election. When the primary steps down, all clients disconnect. This is the intended behavior. While median time to elect a new primary should not typically exceed 12 seconds, make sure any replica configuration changes occur during scheduled maintenance periods.

After these commands return, you have a geographically redundant five-member replica set.

确保副本集有一个主节点。

使用 rs.status() 标识副本集中的主节点。