couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From woh...@apache.org
Subject [couchdb-documentation] branch master updated: Update sharding.rst (#151)
Date Thu, 27 Jul 2017 22:06:45 GMT
This is an automated email from the ASF dual-hosted git repository.

wohali pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/couchdb-documentation.git


The following commit(s) were added to refs/heads/master by this push:
     new a799648  Update sharding.rst (#151)
a799648 is described below

commit a799648373fd70865562e86021774a241534127f
Author: andydonzelli <andydonzelli@users.noreply.github.com>
AuthorDate: Thu Jul 27 23:06:43 2017 +0100

    Update sharding.rst (#151)
    
    * Update sharding.rst
    
    Correcting two instances of "to" should be "too".
    
    * Updating sharding.rst (2)
    
    Fixed a third improper use "to" instead of "too".
---
 src/cluster/sharding.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/cluster/sharding.rst b/src/cluster/sharding.rst
index 57e0d2f..98d946d 100644
--- a/src/cluster/sharding.rst
+++ b/src/cluster/sharding.rst
@@ -267,10 +267,10 @@ time you move a shard. As this can take quite some time, it is not recommended.
 Reshard? No, Preshard!
 ======================
 
-Reshard? Nope. It can not be done. So do not create databases with to few
+Reshard? Nope. It can not be done. So do not create databases with too few
 shards.
 
-If you can not scale out more because you set the number of shards to low, then
+If you can not scale out more because you set the number of shards too low, then
 you need to create a new cluster and migrate over.
 
 #. Build a cluster with enough nodes to handle one copy of your data.
@@ -291,7 +291,7 @@ you need to create a new cluster and migrate over.
 
 Creating more shards than you need and then move the shards around is called
 presharding. The number of shards you need depends on how much data you are
-going to store. But, creating to many shards increases the complexity without
+going to store. But, creating too many shards increases the complexity without
 any real gain. You might even get lower performance. As an example of this, we
 can take the author's (15 year) old lab server. It gets noticeably slower with
 more than one shard and high load, as the hard drive must seek more.

-- 
To stop receiving notification emails like this one, please contact
['"commits@couchdb.apache.org" <commits@couchdb.apache.org>'].

Mime
View raw message