From 36afdb4296c16aa7149a14b2f0a0679c5af8278b Mon Sep 17 00:00:00 2001 From: Andrew Leung Date: Mon, 10 Sep 2012 11:16:53 -0400 Subject: [PATCH 1/3] added in note to specify difference of shard vs shard primary terminating and continued access --- source/faq/sharding.txt | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/source/faq/sharding.txt b/source/faq/sharding.txt index 8cb135e8f58..eef0efdc054 100644 --- a/source/faq/sharding.txt +++ b/source/faq/sharding.txt @@ -343,11 +343,15 @@ Consider the following error message: :program:`mongod` procudes this message if, during a :ref:`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. The :term:`secondary` members of +the shard will elect a new primary member so that the remainder of the +shard data is available for access. If you encounter this issue, contact the `MongoDB User Group `_ or 10gen support to From 53723d49ae87c64cf466f27f4280c709462dba16 Mon Sep 17 00:00:00 2001 From: Andrew Leung Date: Mon, 10 Sep 2012 14:11:32 -0400 Subject: [PATCH 2/3] adding in note about secondary members in moveChunk failure --- source/faq/sharding.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/source/faq/sharding.txt b/source/faq/sharding.txt index eef0efdc054..a054935838c 100644 --- a/source/faq/sharding.txt +++ b/source/faq/sharding.txt @@ -349,9 +349,9 @@ 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 :term:`primary` member of the shard will terminate -itself to prevent data inconsistency. The :term:`secondary` members of -the shard will elect a new primary member so that the remainder of the -shard data is available for access. +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. If you encounter this issue, contact the `MongoDB User Group `_ or 10gen support to From 1b0d93db739fd1ce5f4d5cc7408a96101be0944a Mon Sep 17 00:00:00 2001 From: Andrew Leung Date: Mon, 10 Sep 2012 14:14:05 -0400 Subject: [PATCH 3/3] mentioning that resolution of moveChunk is still required --- source/faq/sharding.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/source/faq/sharding.txt b/source/faq/sharding.txt index a054935838c..6ab0fa637fa 100644 --- a/source/faq/sharding.txt +++ b/source/faq/sharding.txt @@ -351,7 +351,8 @@ 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. +accessible after an election but the chunk migration failure will need +to be resolved. If you encounter this issue, contact the `MongoDB User Group `_ or 10gen support to