couchdb-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vatam...@apache.org
Subject [2/3] documentation commit: updated refs/heads/master to a05f028
Date Wed, 08 Mar 2017 01:59:10 GMT
Fix wording & make ines < 80 chars long


Project: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/commit/b9a63295
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/tree/b9a63295
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-documentation/diff/b9a63295

Branch: refs/heads/master
Commit: b9a632951f8cc072e7ae4ed88dde85ddbdf7059d
Parents: 6edb6ea
Author: Nick Vatamaniuc <vatamane@apache.org>
Authored: Tue Mar 7 20:57:11 2017 -0500
Committer: Nick Vatamaniuc <vatamane@apache.org>
Committed: Tue Mar 7 20:57:11 2017 -0500

----------------------------------------------------------------------
 src/cluster/sharding.rst | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/couchdb-documentation/blob/b9a63295/src/cluster/sharding.rst
----------------------------------------------------------------------
diff --git a/src/cluster/sharding.rst b/src/cluster/sharding.rst
index 7747617..57e0d2f 100644
--- a/src/cluster/sharding.rst
+++ b/src/cluster/sharding.rst
@@ -105,10 +105,10 @@ small there. Let us look in it. Yes, you can get it with curl too:
 
 * ``_id`` The name of the database.
 * ``_rev`` The current revision of the metadata.
-* ``shard_suffix`` The numbers after small and before .couch. The number of
-  seconds after UNIX epoch that the database was created. This is stored as an array of ASCII
codes.
-* ``changelog`` Self explaining. Only for admins to read.
-* ``by_node`` Which shards each node have.
+* ``shard_suffix`` The numbers after small and before .couch. This is seconds
+  after UNIX epoch when the database was created. Stored as ASCII characters.
+* ``changelog`` Self explaining. Mostly used for debugging.
+* ``by_node`` List of shards on each node.
 * ``by_range`` On which nodes each shard is.
 
 Nothing here, nothing there, a shard in my sleeve
@@ -291,10 +291,10 @@ 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 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.
+going to store. But, creating to 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.
 
 How many shards you should have depends, as always, on your use case and your
 hardware. If you do not know what to do, use the default of 8 shards.


Mime
View raw message