Deploy a Replica Set

On this page本页内容

This tutorial describes how to create a three-member replica set from three existing mongod instances running with access control disabled.本教程描述了如何从三个禁用访问控制的现有mongod实例创建一个三成员副本集

To deploy a replica set with enabled access control, see Deploy Replica Set With Keyfile Authentication. 要部署启用了访问控制的副本集,请参阅使用密钥文件身份验证部署副本集If you wish to deploy a replica set from a single MongoDB instance, see Convert a Standalone to a Replica Set. 如果希望从单个MongoDB实例部署副本集,请参阅将独立副本集转换为副本集For more information on replica set deployments, see the Replication and Replica Set Deployment Architectures documentation.有关副本集部署的更多信息,请参阅复制副本集部署体系结构文档。

Overview概述

Three member replica sets provide enough redundancy to survive most network partitions and other system failures. 三个成员副本集提供了足够的冗余,可以承受大多数网络分区和其他系统故障。These sets also have sufficient capacity for many distributed read operations. 这些集合对于许多分布式读取操作也具有足够的容量。Replica sets should always have an odd number of members. 副本集的成员数应始终为奇数。This ensures that elections will proceed smoothly. 这将确保选举顺利进行。For more about designing replica sets, see the Replication overview.有关设计复制集的更多信息,请参阅复制概述

Requirements要求

For production deployments, you should maintain as much separation between members as possible by hosting the mongod instances on separate machines. 对于生产部署,您应该通过在不同的机器上托管mongod实例来尽可能地保持成员之间的隔离。When using virtual machines for production deployments, you should place each mongod instance on a separate host server serviced by redundant power circuits and redundant network paths.在使用虚拟机进行生产部署时,应将每个mongod实例放置在由冗余电源电路和冗余网络路径提供服务的独立主机服务器上。

Before you can deploy a replica set, you must install MongoDB on each system that will be part of your replica set. 在部署副本集之前,必须在将成为副本集一部分的每个系统上安装MongoDB。If you have not already installed MongoDB, see the installation tutorials.如果尚未安装MongoDB,请参阅安装教程

Considerations When Deploying a Replica Set部署副本集时的注意事项

Architecture体系架构

In production, deploy each member of the replica set to its own machine and if possible bind to the standard MongoDB port of 27017.在生产中,将副本集的每个成员部署到自己的机器上,如果可能,绑定到27017的标准MongoDB端口。

See Replica Set Deployment Architectures for more information.有关详细信息,请参阅副本集部署体系结构

Hostnames主机名

Important重要

To avoid configuration updates due to IP address changes, use DNS hostnames instead of IP addresses. 为了避免由于IP地址更改而导致的配置更新,请使用DNS主机名而不是IP地址。It is particularly important to use a DNS hostname instead of an IP address when configuring replica set members or sharded cluster members.在配置副本集成员或分片群集成员时,使用DNS主机名而不是IP地址尤为重要。

Use hostnames instead of IP addresses to configure clusters across a split network horizon. 使用主机名而不是IP地址来跨拆分的网络范围配置群集。Starting in MongDB 5.0, nodes that are only configured with an IP address will fail startup validation and will not start.从MongDB 5.0开始,仅配置IP地址的节点将无法启动验证,无法启动。

IP BindingIP绑定

Use the --bind_ip option to ensure that MongoDB listens for connections from applications on configured addresses.使用--bind_ip选项确保MongoDB侦听来自配置地址上的应用程序的连接。

Changed in version 3.6.在版本3.6中更改

Warning警告
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. 在绑定到非本地主机(例如,可公开访问的)IP地址之前,请确保已保护您的集群免受未经授权的访问。For a complete list of security recommendations, see Security Checklist. 有关安全建议的完整列表,请参阅安全检查表At minimum, consider enabling authentication and hardening network infrastructure.至少要考虑启用身份验证加强网络基础设施
MongoDB binaries, mongod and mongos, bind to localhost by default. MongoDB二进制文件mongodmongos默认绑定到localhost。If the net.ipv6 configuration file setting or the --ipv6 command line option is set for the binary, the binary additionally binds to the localhost IPv6 address.如果为二进制文件设置了net.ipv6配置文件设置或--ipv6命令行选项,则该二进制文件还将绑定到本地主机ipv6地址。By default mongod and mongos that are bound to localhost only accept connections from clients that are running on the same computer. 默认情况下,绑定到localhost的mongodmongos只接受来自同一台计算机上运行的客户端的连接。This binding behavior includes mongosh and other members of your replica set or sharded cluster. 这种绑定行为包括mongosh和复制集或分片集群的其他成员。Remote clients cannot connect to binaries that are bound only to localhost.远程客户端无法连接到仅绑定到localhost的二进制文件。To override the default binding and bind to other IP addresses, use the net.bindIp configuration file setting or the --bind_ip command-line option to specify a list of hostnames or IP addresses.要覆盖默认绑定并绑定到其他IP地址,请使用net.bindIp配置文件设置或--bind_IP命令行选项指定主机名或IP地址列表。
Warning警告
Starting in MongDB 5.0, split horizon DNS nodes that are only configured with an IP address fail startup validation and report an error. 从MongDB 5.0开始,仅配置了IP地址的拆分地平线DNS节点无法启动验证并报告错误。See disableSplitHorizonIPCheck.请参见disableSplitHorizonIPCheck
For example, the following mongod instance binds to both the localhost and the hostname My-Example-Associated-Hostname, which is associated with the IP address 198.51.100.1:例如,以下mongod实例绑定到本地主机和主机名My-Example-Associated-Hostname,该主机名与IP地址198.51.100.1关联:
mongod --bind_ip localhost,My-Example-Associated-Hostname
In order to connect to this instance, remote clients must specify the hostname or its associated IP address 198.51.100.1:为了连接到此实例,远程客户端必须指定主机名或其关联的IP地址198.51.100.1
mongosh --host My-Example-Associated-Hostname
mongosh --host 198.51.100.1

Connectivity连通性

Ensure that network traffic can pass securely between all members of the set and all clients in the network .确保网络流量可以在集合的所有成员和网络中的所有客户端之间安全传递。

Consider the following:考虑以下内容:

  • Establish a virtual private network. 建立虚拟专用网络。Ensure that your network topology routes all traffic between members within a single site over the local area network.确保您的网络拓扑通过局域网在单个站点内的成员之间路由所有通信。
  • Configure access control to prevent connections from unknown clients to the replica set.配置访问控制以防止从未知客户端到副本集的连接。
  • Configure networking and firewall rules so that incoming and outgoing packets are permitted only on the default MongoDB port and only from within your deployment. 配置网络和防火墙规则,以便仅在默认MongoDB端口上允许传入和传出数据包,并且只允许从部署中传入和传出。See the IP Binding considerations.请参阅IP绑定注意事项。

Ensure that each member of a replica set is accessible by way of resolvable DNS or hostnames. 确保可以通过可解析DNS或主机名访问副本集的每个成员。You should either configure your DNS names appropriately or set up your systems' /etc/hosts file to reflect this configuration.您应该适当配置DNS名称或设置系统的/etc/hosts文件以反映此配置。

Each member must be able to connect to every other member. 每个成员必须能够连接到其他每个成员。For instructions on how to check your connection, see Test Connections Between all Members.有关如何检查连接的说明,请参阅测试所有成员之间的连接

Configuration配置

Create the directory where MongoDB stores data files before deploying MongoDB.在部署MongoDB之前,创建MongoDB存储数据文件的目录。

Specify the mongod configuration in a configuration file stored in /etc/mongod.conf or a related location./etc/mongod.conf或相关位置中存储的配置文件中指定mongod配置。

For more information about configuration options, see Configuration File Options.有关配置选项的详细信息,请参阅配置文件选项

Procedure过程

The following procedure outlines the steps to deploy a replica set when access control is disabled.以下过程概述了在禁用访问控制时部署副本集的步骤。

1

Start each member of the replica set with the appropriate options.使用适当的选项启动复制副本集的每个成员。

For each member, start a mongod instance with the following settings:对于每个成员,使用以下设置启动mongod实例:

  • Set replication.replSetName option to the replica set name. replication.replSetName选项设置为副本集名称。If your application connects to more than one replica set, each set must have a distinct name.如果应用程序连接到多个副本集,则每个副本集必须具有不同的名称。
  • Set net.bindIp option to the hostname/ip or a comma-delimited list of hostnames/ips.net.bindIp选项设置为主机名/ip或以逗号分隔的主机名/ips列表。
  • Set any other settings as appropriate for your deployment.根据部署情况设置任何其他设置。

In this tutorial, the three mongod instances are associated with the following hosts:在本教程中,三个mongod实例与以下主机关联:

Replica Set Member副本集成员Hostname
Member 0mongodb0.example.net
Member 1mongodb1.example.net
Member 2mongodb2.example.net

The following example specifies the replica set name and the ip binding through the --replSet and --bind_ip command-line options:以下示例通过--replSet--bind_ip命令行选项指定副本集名称和ip绑定:

Warning警告

Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. 在绑定到非本地主机(例如,可公开访问的)IP地址之前,请确保已保护您的集群免受未经授权的访问。For a complete list of security recommendations, see Security Checklist. 有关安全建议的完整列表,请参阅安全检查表At minimum, consider enabling authentication and hardening network infrastructure.至少要考虑启用身份验证加强网络基础设施

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

For <hostname(s)|ip address(es)>, specify the hostname(s) and/or ip address(es) for your mongod instance that remote clients (including the other members of the replica set) can use to connect to the instance.对于<hostname(s)|ip address(es)>,指定远程客户端(包括副本集的其他成员)可以用来连接到实例的mongod实例的主机名和/或ip地址。

Alternatively, you can also specify the replica set name and the ip addresses in a configuration file:或者,您也可以在配置文件中指定副本集名称ip地址

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

To start mongod with a configuration file, specify the configuration file's path with the --config option:要使用配置文件启动mongod,请使用--config选项指定配置文件的路径:

mongod --config <path-to-config>

In production deployments, you can configure a init script to manage this process. 在生产部署中,您可以配置init脚本来管理此过程。Init scripts are beyond the scope of this document.初始化脚本超出了本文档的范围。

2

Connect mongosh to one of the mongod instances.mongosh连接到其中一个mongod实例。

From the same machine where one of the mongod is running (in this tutorial, mongodb0.example.net), start mongosh. 从运行其中一个mongod的同一台机器(在本教程中为mongodb0.example.net),启动mongoshTo connect to the mongod listening to localhost on the default port of 27017, simply issue:要在默认端口27017上连接到监听本地主机的mongod,只需发出:

mongo

Depending on your path, you may need to specify the path to the mongosh binary.根据您的路径,您可能需要指定mongosh二进制文件的路径。

3

Initiate the replica set.启动复制集。

From mongosh, run rs.initiate() on replica set member 0.mongosh,对副本集成员0运行rs.initiate()

Important重要

Run rs.initiate() on just one and only onemongod instance for the replica set.仅在副本集的一个且仅一个mongod实例上运行rs.initiate()

Important重要

To avoid configuration updates due to IP address changes, use DNS hostnames instead of IP addresses. 为了避免由于IP地址更改而导致的配置更新,请使用DNS主机名而不是IP地址。It is particularly important to use a DNS hostname instead of an IP address when configuring replica set members or sharded cluster members.在配置副本集成员或分片群集成员时,使用DNS主机名而不是IP地址尤为重要。

Use hostnames instead of IP addresses to configure clusters across a split network horizon. 使用主机名而不是IP地址来跨拆分的网络范围配置群集。Starting in MongDB 5.0, nodes that are only configured with an IP address will fail startup validation and will not start.从MongDB 5.0开始,仅配置IP地址的节点将无法启动验证,无法启动。

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 initiates a replica set, using the default replica set configuration.MongoDB使用默认副本集配置启动副本集。

4

View the replica set configuration.查看副本集配置。

Use rs.conf() to display the replica set configuration object:使用rs.conf()显示副本集配置对象

rs.conf()

The replica set configuration object resembles the following:副本集配置对象类似于以下内容:

{
   "_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")
   }
}
5

Ensure that the replica set has a primary.确保副本集具有主副本。

Use rs.status() to identify the primary in the replica set.使用rs.status()标识副本集中的主副本。

←  Replica Set Deployment TutorialsDeploy a Replica Set for Testing and Development →