Skip to content

DOCS-1280 remove references to noMoveParanoia #834

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.

Sign up for GitHub

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

DOCS-1280 remove references to noMoveParanoia #834

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 1 addition & 4 deletions source/faq/sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,9 +186,6 @@ Yes. :program:`mongod` creates these files as backups during normal

Once these migrations are complete, you may delete these files.

You can set :setting:`noMoveParanoia` to ``true`` to disable this
behavior.

How does ``mongos`` use connections?
------------------------------------

Expand Down Expand Up @@ -375,7 +372,7 @@ the hash of a key with an ascending value.

You can use a :ref:`hashed index <index-type-hashed>` and
:term:`hashed shard key`
or you can compute and maintain this hashed value in your
or you can compute and maintain this hashed value in your
application.

What do ``moveChunk commit failed`` errors mean?
Expand Down
13 changes: 0 additions & 13 deletions source/reference/configuration-options.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -807,19 +807,6 @@ Sharded Cluster Options
these instances is ``27018``. The only affect of
:setting:`shardsvr` is to change the port number.

.. setting:: noMoveParanoia

*Default:* false

When set to ``true``, :setting:`noMoveParanoia` disables a
"paranoid mode" for data writes for chunk migration operation. See
the :ref:`chunk migration <sharding-chunk-migration>` and
:dbcommand:`moveChunk` command documentation for more information.

By default :program:`mongod` will save copies of migrated chunks on
the "from" server during migrations as "paranoid mode." Setting
this option disables this paranoia.

.. setting:: configdb

*Default:* None.
Expand Down
11 changes: 0 additions & 11 deletions source/reference/mongod.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -639,17 +639,6 @@ Sharding Cluster Options
``27018``. The only effect of :option:`--shardsvr` is to change
the port number.

.. option:: --noMoveParanoia

Disables a "paranoid mode" for data writes for chunk migration
operation. See the
:ref:`chunk migration <sharding-chunk-migration>`
and :dbcommand:`moveChunk` command documentation for more information.

By default :program:`mongod` will save copies of migrated chunks on
the "from" server during migrations as "paranoid mode." Setting
this option disables this paranoia.

SSL Options
```````````

Expand Down