Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
77 lines (58 sloc) 2.49 KB
.. index:: replica set members; hidden
.. _replica-set-hidden-configuration:
.. _replica-set-hidden-members:
Hidden Replica Set Members
.. default-domain:: mongodb
.. contents:: On this page
:backlinks: none
:depth: 1
:class: singlecol
A hidden member maintains a copy of the :term:`primary's <primary>`
data set but is **invisible** to client applications. Hidden members
are good for workloads with different usage patterns from the other
members in the :term:`replica set`. Hidden members must always be
:ref:`priority 0 members <replica-set-secondary-only-members>` and
so **cannot become primary**. The :method:`db.isMaster()` method does not
display hidden members. Hidden members, however, **may vote** in
:ref:`elections <replica-set-elections>`.
In the following five-member replica set, all four secondary members
have copies of the primary's data set, but one of the secondary members
is hidden.
.. include:: /images/replica-set-hidden-member.rst
Read Operations
Clients will not distribute reads with the appropriate :doc:`read
preference </core/read-preference>` to hidden members. As a result, these
members receive no traffic other than basic replication. Use hidden
members for dedicated tasks such as reporting and
backups. :doc:`Delayed members </core/replica-set-delayed-member>`
should be hidden.
In a sharded cluster, :binary:`~bin.mongos` do not interact with hidden
Hidden members *may* vote in replica set elections. If you stop a
voting hidden member, ensure that the set has an active majority or the
:term:`primary` will step down.
For the purposes of backups,
- .. include:: /includes/extracts/wt-fsync-lock-compatibility.rst
Write Concern
Hidden replica set members can acknowledge write operations issued
with :writeconcern:`w: \<number\> <\<number\>>`. For write operations
isued with :writeconcern:`w : "majority" <"majority">`, however,
hidden members must also be voting members (i.e. :rsconf:`members[n].votes`
greater than ``0``) to acknowledge the ``"majority"`` write operation.
Non-voting replica set members (i.e. :rsconf:`members[n].votes`
is ``0``) cannot contribute to acknowledging write operations with
``majority`` write concern.
Further Reading
For more information about backing up MongoDB databases,
see :doc:`/core/backups`. To configure a hidden member, see
You can’t perform that action at this time.