Skip to content

removing incorrect section #2036

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

removing incorrect section #2036

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
28 changes: 0 additions & 28 deletions source/core/tag-aware-sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
</tutorial/split-chunks-in-sharded-cluster>`. You can then manually
migrate chunks to the appropriate shards, or wait for the balancer to
automatically migrate these chunks.