diff --git a/source/faq/replica-sets.txt b/source/faq/replica-sets.txt index 1f8afc34fd1..269eefa6859 100644 --- a/source/faq/replica-sets.txt +++ b/source/faq/replica-sets.txt @@ -34,7 +34,7 @@ inaccessible, the other members can autonomously :term:`elect ` one of the other members of the set to be the new "primary". By default, clients send all reads to the primary; -however, ":term:`read preference`" is configurable at the +however, :term:`read preference` is configurable at the client level on a per-connection basis, which makes it possible to send reads to secondary nodes instead. @@ -78,7 +78,7 @@ For example, a deployment may maintain a :term:`primary` and :term:`secondary` in an East-coast data center along with a :term:`secondary` member for disaster recovery in a West-coast data center. -.. seealso:: ":doc:`/tutorial/deploy-geographically-distributed-replica-set`" +.. seealso:: :doc:`/tutorial/deploy-geographically-distributed-replica-set` Can MongoDB replicate over a "noisy" connection? ------------------------------------------------ @@ -206,10 +206,19 @@ Which members of a replica set vote in elections? ------------------------------------------------- All members of a replica set, unless the value of :data:`votes -` is equal to ``0`` vote in elections. This includes +` is equal to ``0``, vote in elections. This includes all :ref:`delayed `, :ref:`hidden -` and all :ref:`secondary-only -` members as well as the +` and :ref:`secondary-only +` members, as well as the :ref:`arbiters `. .. seealso:: :ref:`replica-set-elections` + +What is the default voting behavior for hidden members? +------------------------------------------------------- + +By default, hidden members of replica sets *do* vote in elections. To +change this behavior, change the hidden member's :data:`votes +` field to ``0``. + +.. seealso:: :ref:`replica-set-elections`