@@ -31,9 +31,9 @@ exceptional situations may cause secondaries lag behind further. See
31
31
Also consider :ref:`oplog sizing <replica-set-oplog-sizing>` for more
32
32
information about the oplog.
33
33
34
- All nodes send heartbeats to all other nodes , and can import
35
- operations to into its oplog from any other node in the
36
- cluster .
34
+ All members send heartbeats to all other members , and can import
35
+ operations to into its oplog from any other member in the
36
+ set .
37
37
38
38
.. In 2.0, replicas would import entries from the member lowest
39
39
.. "ping," This wasn't true in 1.8 and will likely change in 2.2.
@@ -115,15 +115,15 @@ modify the configuration of an existing replica set.
115
115
Elections
116
116
---------
117
117
118
- When you initialize a replica set for the first time, or when any
118
+ When you initialize a :term:` replica set` for the first time, or when any
119
119
failover occurs, an election takes place to decide which member should
120
120
become :term:`primary`. A primary is the only member in the replica
121
- set that can accept write commands such as :func:`insert()
121
+ set that can accept write operations including :func:`insert()
122
122
<db.collection.insert()>`, :func:`update() <db.collection.update()>`,
123
- and :func:`remove() <db.collection.remove`.
123
+ and :func:`remove() <db.collection.remove()> `.
124
124
125
125
Elections are the process replica set members use to
126
- select the primary in a cluster . Elections follow two events:
126
+ select the primary in a set . Elections follow after one of two events:
127
127
a primary that "steps down" or a :term:`secondary` that
128
128
loses contact with a :term:`primary` member. All members have one vote
129
129
in an election, and any :program:`mongod` can veto an election. A
0 commit comments