From ca155dfb8eaaea8ec4e90c3463958d99c003e227 Mon Sep 17 00:00:00 2001 From: Nick Geoghegan Date: Fri, 19 Apr 2013 12:57:18 +0200 Subject: [PATCH] Readability improvements. --- source/core/tag-aware-sharding.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/core/tag-aware-sharding.txt b/source/core/tag-aware-sharding.txt index cd0a3c52626..e3eb9ffddf1 100644 --- a/source/core/tag-aware-sharding.txt +++ b/source/core/tag-aware-sharding.txt @@ -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 @@ -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