From 04cf2de36561ad2424d5aa692e4e62139f773525 Mon Sep 17 00:00:00 2001 From: Asya Kamsky Date: Tue, 14 Oct 2014 20:43:59 -0400 Subject: [PATCH] removing incorrect section This hasn't been the case since 2.2 - see SERVER-7668 which fixed it for 2.3.2. --- source/core/tag-aware-sharding.txt | 28 ---------------------------- 1 file changed, 28 deletions(-) diff --git a/source/core/tag-aware-sharding.txt b/source/core/tag-aware-sharding.txt index 8dbb122ac0a..bcbb029ccd8 100644 --- a/source/core/tag-aware-sharding.txt +++ b/source/core/tag-aware-sharding.txt @@ -57,31 +57,3 @@ Once configured, the balancer respects tag ranges during future :doc:`/tutorial/administer-shard-tags` -Chunks that Span Multiple Tag Ranges ------------------------------------- - -A single chunk may contain data with a :term:`shard key` values that -falls into ranges associated with more than one tag. To accommodate -these situations, the balancer may migrate chunks to shards that -contain shard key values that exceed the upper bound of the selected -tag range. - -.. example:: - - Given a sharded collection with two configured tag ranges: - - - :term:`Shard key` values between ``100`` and ``200`` have tags to - direct corresponding chunks to shards tagged ``NYC``. - - - Shard key values between ``200`` and ``300`` have tags to - direct corresponding chunks to shards tagged ``SFO``. - - For this collection cluster, the balancer will migrate a chunk with :term:`shard - key` values ranging between ``150`` and ``220`` to a shard tagged - ``NYC``, since ``150`` is closer to ``200`` than ``300``. - -To ensure that your collection has no potentially ambiguously tagged -chunks, :doc:`create splits on your tag boundaries -`. You can then manually -migrate chunks to the appropriate shards, or wait for the balancer to -automatically migrate these chunks.