Skip to content

DOCS-10966 - Updating image for sharding low cardinality #3075

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

DOCS-10966 - Updating image for sharding low cardinality #3075

Show file tree
Hide file tree
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
14 changes: 7 additions & 7 deletions source/core/sharding-shard-key.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ For instructions specific to sharding a collection using the
:ref:`hashed sharding <sharding-hashed>` strategy, see
:ref:`deploy-hashed-sharded-cluster-shard-collection`

For instructions specific to sharding a collection using the
For instructions specific to sharding a collection using the
:ref:`ranged sharding <sharding-ranged>` strategy, see
:ref:`deploy-ranged-sharded-cluster-shard-collection`.

Expand Down Expand Up @@ -166,14 +166,14 @@ Shard Key Cardinality
~~~~~~~~~~~~~~~~~~~~~

The :term:`cardinality` of a shard key determines the maximum number of chunks
the balancer can create. This can reduce or remove the effectiveness of
the balancer can create. This can reduce or remove the effectiveness of
horizontal scaling in the cluster.

A unique shard key value can exist on no more than a single chunk at any
given time. If a shard key has a cardinality of ``4``, then there can
be no more than ``4`` chunks within the sharded cluster, each storing
one unique shard key value. This constrains the number of effective
shards in the cluster to ``4`` as well - adding additional shards would
A unique shard key value can exist on no more than a single chunk at any
given time. If a shard key has a cardinality of ``4``, then there can
be no more than ``4`` chunks within the sharded cluster, each storing
one unique shard key value. This constrains the number of effective
shards in the cluster to ``4`` as well - adding additional shards would
not provide any benefit.

The following image illustrates a sharded cluster using the field
Expand Down
Loading