Redirect voting

source/administration/replication-architectures.txt

@@ -132,10 +132,10 @@ for these kinds of nodes:
   <replica-set-hidden-members>`.)
 
 - **Voting**: This changes the number of votes that a member of the
-  set node has in elections for primary. In general use priority to
+  replica set has in elections. In general, use priority to
   control the outcome of elections, as weighting votes introduces
-  operational complexities and risks set failure. Only modify the
-  number of votes, if you need to have more than 7 members of a
+  operational complexities and risks. Only modify the
+  number of votes when you need to have more than 7 members in a
   replica set. (:ref:`see also <replica-set-non-voting-members>`.)
 
 .. note::

source/core/replication-internals.txt

@@ -31,9 +31,9 @@ exceptional situations may cause secondaries lag behind further. See
 Also consider :ref:`oplog sizing <replica-set-oplog-sizing>` for more
 information about the oplog.
 
-All nodes send heartbeats to all other nodes, and can import
-operations to into its oplog from any other node in the
-cluster.
+All members send heartbeats to all other members, and can import
+operations to into its oplog from any other member in the
+set.
 
 .. In 2.0, replicas would import entries from the member lowest
 .. "ping," This wasn't true in 1.8 and will likely change in 2.2.
@@ -115,82 +115,93 @@ modify the configuration of an existing replica set.
 Elections
 ---------
 
-When you initialize a replica set for the first time, and when
-any failover occurs, an election takes place to decide which
-member should become primary.
+When you initialize a :term:`replica set` for the first time, or when any
+failover occurs, an election takes place to decide which member should
+become :term:`primary`. A primary is the only member in the replica
+set that can accept write operations including :func:`insert()
+<db.collection.insert()>`, :func:`update() <db.collection.update()>`,
+and :func:`remove() <db.collection.remove()>`.
 
-Elections are the process that the members of a replica set use to
-select the primary node in a cluster. Elections follow two events:
-a primary node that "steps down" or a :term:`secondary` member that
-loses contact with a :term:`primary` node. All members have one vote
-in an election, and every :program:`mongod` can veto an election. A
-single member's veto will invalidate the election.
+Elections are the process replica set members use to
+select the primary in a set. Elections follow after one of two events:
+a primary that "steps down" or a :term:`secondary` that
+loses contact with a :term:`primary` member. All members have one vote
+in an election, and any :program:`mongod` can veto an election. A
+single veto will invalidate the election.
 
 An existing primary will step down in response to the
 :dbcommand:`replSetStepDown` command, or if it sees that one of
 the current secondaries is eligible for election *and* has a higher
-priority. A secondary node will call for an election if it cannot
-establish a connection to a primary node. Primary nodes will also step
+priority. A secondary will call for an election if it cannot
+establish a connection to a primary member. A primary will also step
 down when they cannot contact a majority of the members of the replica
-set. When the current primary steps down, it closes all open client
+set. When the current primary member steps down, it closes all open client
 connections to prevent clients from unknowingly writing data to a
-non-primary node.
+non-primary member.
 
 In an election, every member, including :ref:`hidden
 <replica-set-hidden-members>` members, :ref:`arbiters
-<replica-set-arbiters>`, and even recovering nodes get a single
-vote. Members will give votes to every eligible node that calls an
+<replica-set-arbiters>`, and even recovering members get a single
+vote. Members will give votes to every eligible member that calls an
 election.
 
 A member of the set will veto an election under the following
 conditions:
 
-- If the node seeking an election is not a member of the voter's set.
+- If the member seeking an election is not a member of the voter's set.
 
-- If the node seeking an election is not up to date with the most
+- If the member seeking an election is not up to date with the most
   recent operation accessible in the replica set.
 
-- If the node seeking an election has a lower priority than another node
+- If the member seeking an election has a lower priority than another member
   in the set that is also eligible for election.
 
-- If the current :term:`primary` node has more recent operations
-  (i.e. a higher "optime") than the node seeking election, from the
-  perspective of the voting node.
+- If the current :term:`primary` member has more recent operations
+  (i.e. a higher "optime") than the member seeking election, from the
+  perspective of the voting member.
 
 - The current primary will also veto an election if it has the same or
   more recent operations (i.e. a "higher or equal optime") than the
   node seeking election.
 
 .. note::
 
-   All members of a replica set *can* veto an election, even if they
+   Any member of a replica set *can* veto an election, even if they
    are :ref:`non-voting members <replica-set-non-voting-members>`.
 
-The first node to receive votes from a majority of members in a set
+The first member to receive votes from a majority of members in a set
 becomes the next primary until the next election. Be
 aware of the following conditions and possible situations:
 
 - Replica set members send heartbeats (pings) to each other every 2
   seconds. If a heartbeat does not return for more than 10 seconds,
-  the other nodes mark the delinquent node as inaccessible.
+  the other members mark the delinquent member as inaccessible.
 
 - Replica set members only compare priorities with other members of
   the set. The absolute value of priorities does not have any impact on
   the outcome of replica set elections.
 
   .. note::
 
-     The only exception is that members with a priority of ``0`` cannot
-     become :term:`primary` and will not seek election.
+     The only exception is that members with a priority of ``0``
+     cannot become :term:`primary` and will not seek election. See
+     :ref:`replica-set-node-priority-configuration` for more
+     information.
 
 - Replica set members cannot become primary *unless* they have the
   highest "optime" of any visible members in the set.
 
 - If the member of the set with the highest priority is within 10
   seconds of the latest oplog entry, then the set will *not* elect a
-  :term:`primary` until the node with the highest priority catches up
+  :term:`primary` until the member with the highest priority catches up
   to the latest operation.
 
+
+.. seealso:: ":ref:`Non-voting members in a replica
+             set<replica-set-non-voting-members>`",
+             ":ref:`replica-set-node-priority-configuration`", and
+             ":data:`replica configuration <members[n].votes>`
+
 Syncing
 -------
 

source/core/replication.txt

@@ -170,11 +170,11 @@ participate in :term:`elections <election>`.
 Non-Voting
 ~~~~~~~~~~
 
-You may choose to change the number of votes that each node has in
+You may choose to change the number of votes that each member has in
 :term:`elections <election>` for :term:`primary`. In general, all
-nodes should have only 1 vote to prevent intermittent ties, deadlock,
+members should have only 1 vote to prevent intermittent ties, deadlock,
 or the wrong nodes from becoming :term:`primary`. Use ":ref:`replica
-set priorities <replica-set-node-priority>`" to control which nodes
+set priorities <replica-set-node-priority>`" to control which members
 are more likely to become primary.
 
 .. index:: pair: replica set; failover
@@ -247,8 +247,6 @@ have a single vote in :ref:`elections <replica-set-elections>`.
    :data:`members[n].votes` except to permit more than 7 secondary
    nodes.
 
-.. COMMENT a bit unclear. ALWAYS set, but except to have more than 7 secondary?
-
 .. seealso:: ":ref:`Node Priority Configuration <replica-set-node-priority-configuration>`"
 
 .. index:: pair: replica set; consistency

source/reference/replica-configuration.txt

@@ -174,9 +174,12 @@ Configuration Variables
    **Default**: 1
 
    Controls the number of votes a server has in a :ref:`replica set
-   election <replica-set-elections>`. If you need more than 7 nodes,
-   use this setting to add additional non-voting nodes with a
-   :data:`members[n].votes` value of ``0``.
+   election <replica-set-elections>`. The number of votes each member
+   has can be any non-negative integer, but it is highly recommended
+   each member has 1 or 0 votes.
+
+   If you need more than 7 members, use this setting to add additional
+   non-voting members with a :data:`members[n].votes` value of ``0``.
 
    For most deployments and most members, use the default value,
    ``1``, for :data:`members[n].votes`.

source/tutorial/expand-replica-set.txt

@@ -126,4 +126,12 @@ Production Notes
     :term:`primary` member's :term:`oplog`. The new secondary must be
     able to become current using operations from the primary's oplog.
 
+- There is a maximum of seven :ref:`voting members
+  <replica-set-election-internals>` in any replica set. When adding
+  more members to a replica set that already has seven votes, you must
+  either:
 
+  - add the new member as a :ref:`non-voting members
+    <replica-set-non-voting-members>` or,
+
+  - remove votes from an :data:`existing member <members[n].votes>`.