Skip to content

DOCS-2706 add arbiter config options #1698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions source/tutorial/add-replica-set-arbiter.txt
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,31 @@ server, monitoring host.
Do not run an arbiter on the same system as a member of the replica
set.

Considerations
--------------

An arbiter does not store data, but until the arbiter's :program:`mongod`
process is added to the replica set, the arbiter will act like any other
:program:`mongod` process and start up with a set of data files and with a
full-sized :term:`journal`. To minimize the default creation of data, set
the following options to ``true`` in the arbiter's :doc:`configuration
file </reference/configuration-options>`:

- :setting:`nojournal`

.. warning::

Never set :setting:`nojournal` to ``true`` on a data-bearing node.

- :setting:`smallfiles`

- :setting:`noprealloc`

These settings are specific to arbiters. Do not set :setting:`nojournal`
to ``true`` on a data-bearing node. Similarly, do not set
:setting:`smallFiles` or :setting:`noprealloc` unless specifically
indicated.

Add an Arbiter
--------------

Expand Down