Skip to content

Readability improvements. #882

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.

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
Changes from all commits
Commits
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
8 changes: 4 additions & 4 deletions source/core/tag-aware-sharding.txt
Original file line number Diff line number Diff line change
Expand Up @@ -14,9 +14,9 @@ cluster. This capability enables the following deployment patterns:

- isolating a specific subset of data on specific set of shards.

- controlling the balancing policy so that in a geographically
distributed cluster the most relevant portions of the data set
reside on the shards with greatest proximity to the application
- controlling the balancing policy so that, in a geographically
distributed cluster, the most relevant portions of the data set
reside on the shards with the greatest proximity to the application
servers.

This document describes the behavior, operation, and use of tag aware
Expand Down Expand Up @@ -65,7 +65,7 @@ tags, if tagged shards are not balanced. [#specific-tagged-migrations]_
values ranging between ``150`` and ``220`` to a shard tagged
``NYC``, since ``150`` is closer to ``200`` than ``300``.

After configuring tags on shards and ranges of the shard key, the
After configuring tags on the shards and ranges of the shard key, the
cluster may take some time to reach the proper distribution of data,
depending on the division of chunks (i.e. splits) and the current
distribution of data in the cluster. Once configured, the balancer
Expand Down