Skip to content

DOCS-114 - Touchup FAQ moving chunks #208

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

Merged
merged 3 commits into from
Sep 11, 2012
Merged

DOCS-114 - Touchup FAQ moving chunks #208

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
36afdb4
added in note to specify difference of shard vs shard primary termina…
Sep 10, 2012
53723d4
adding in note about secondary members in moveChunk failure
Sep 10, 2012
1b0d93d
mentioning that resolution of moveChunk is still required
Sep 10, 2012
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
11 changes: 8 additions & 3 deletions source/faq/sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,11 +343,16 @@ Consider the following error message:

:program:`mongod` procudes this message if, during a :ref:`chunk
migration <sharding-chunk-migration>`, the :term:`shard` could not
connect to the :term:`config database` to update chunk information. If
connect to the :term:`config database` to update chunk information at
the end of the migration process. If
the shard cannot update the config database after
:dbcommand:`moveChunk`, the shard cluster will have an inconsistent
view of all chunks. For this situation, the shard will terminate
itself to prevent data inconsistency.
view of all chunks. For this situation, the :term:`primary` member of
the shard will terminate
itself to prevent data inconsistency. If the config database is
accessible by the :term:`secondary` members, the shard's data will be
accessible after an election but the chunk migration failure will need
to be resolved.

If you encounter this issue, contact the `MongoDB User Group
<http://groups.google.com/group/mongodb-user>`_ or 10gen support to
Expand Down