@@ -548,7 +548,7 @@ However, you may want to migrate chunks manually in a few cases:
548
548
- If the balancer in an active cluster cannot distribute chunks within
549
549
the balancing window, then you will have to migrate chunks manually.
550
550
551
- To migrate chunks, use the :dbcommand:`moveChunk` command.
551
+ To migrate chunks, use the :dbcommand:`moveChunk` command.
552
552
553
553
.. note::
554
554
@@ -577,22 +577,26 @@ This command moves the chunk that includes the shard key value "smith" to the
577
577
block until the migration is complete.
578
578
579
579
.. versionadded:: 2.2
580
- :dbcommand:`moveChunk` command now has the : ``_secondaryThrottle``
580
+ :dbcommand:`moveChunk` command has the: ``_secondaryThrottle``
581
581
paramenter. When set to ``true``, MongoDB ensures that
582
582
:term:`secondary` members have replicated operations before allowing
583
583
new chunk migrations.
584
584
585
585
.. warning::
586
586
587
- The :dbcommand:`moveChunk` command may produce an error message:
587
+ The :dbcommand:`moveChunk` command may produce the following error
588
+ message:
588
589
589
590
.. code-block:: none
590
591
591
592
The collection's metadata lock is already taken.
592
593
593
- when there are open :term:`cursors <cursor>` accessing the chunk to
594
- be moved. To fix this situation, either wait until the cursors
595
- complete their operation or remove the cursors.
594
+ These errors occur when clients have too many open :term:`cursors
595
+ <cursor>` that access the chunk you are migrating. You can either
596
+ wait until the cursors complete their operation or close the
597
+ cursors manually.
598
+
599
+ .. TODO insert link to killing a cursor.
596
600
597
601
.. index:: balancing; operations
598
602
.. _sharding-balancing-operations:
@@ -718,8 +722,8 @@ be able to migrate chunks:
718
722
patterns, it is important to ensure that the balancing window you
719
723
select will be sufficient to support the needs of your deployment.
720
724
721
- Remove Balancing Window Schedule
722
- --------------------------------
725
+ Remove a Balancing Window Schedule
726
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
723
727
724
728
If you have :ref:`set the balancing window
725
729
<sharding-schedule-balancing-window>` and wish to remove the schedule
0 commit comments