On this page本页内容
rs.
initiate
(configuration)¶Initiates a replica set. Optionally, the method can take an argument in the form of a document that holds the configuration of a replica set.
The rs.initiate()
method has the following parameter:
configuration |
document |
The rs.initiate()
method provides a wrapper around the replSetInitiate
command.
Starting in MongoDB 3.6, MongoDB binaries, mongod
and mongos
, bind to localhost by default. 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.
Previously, starting from MongoDB 2.6, only the binaries from the official MongoDB RPM (Red Hat, CentOS, Fedora Linux, and derivatives) and DEB (Debian, Ubuntu, and derivatives) packages bind to localhost by default.
When bound only to the localhost, these MongoDB 3.6 binaries can only accept connections from clients (including the mongo
shell, other members in your deployment for replica sets and sharded clusters)
that are running on the same machine. Remote clients cannot connect to the binaries bound only to localhost.
To override and bind to other ip addresses, you can use the net.bindIp
configuration file setting or the --bind_ip
command-line option to specify a list of hostnames or ip addresses.
Warning
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.
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
:
In order to connect to this instance, remote clients must specify the hostname or its associated ip address 198.51.100.1
:
See Replica Set Configuration Document Example for details of replica set configuration document.
Tip
When possible, use a logical DNS hostname instead of an ip address, particularly when configuring replica set members or sharded cluster members. The use of logical DNS hostnames avoids configuration changes due to ip address changes.
The following example initiates a new replica set with three members.
The three mongod
instances must have started with the --replSet
command line option (or replication.replSetName
if using a configuration file) set to myReplSet
and the --bind_ip
(or net.bindIp
if using a configuration file) set appropriately such that other members of the replica set and clients can connect.
Warning
Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.
Connect a mongo
shell to one of the mongod
instances and run rs.initiate()
.
Note
Run rs.initiate()
on just one and only one
mongod
instance for the replica set.
Tip
When possible, use a logical DNS hostname instead of an ip address, particularly when configuring replica set members or sharded cluster members. The use of logical DNS hostnames avoids configuration changes due to ip address changes.
For details on replica set configuration, see Replica Set Configuration Fields.
For details on deploying a replica set, see Deploy a Replica Set.
See also参阅