diff options
| author | Drago Rosson <drago@rosson.me> | 2015-07-28 20:27:35 +0300 |
|---|---|---|
| committer | Drago Rosson <drago@rosson.me> | 2015-07-28 20:29:50 +0300 |
| commit | 6976f20e83953c141a550faed45801bb67548f7a (patch) | |
| tree | c4ec0c9e9512b55f422a30db599de0ec73fdc5d2 /mongodb | |
| parent | 6a57cb89821ff338e9104fbec0a00988025f49af (diff) | |
Proof MongoDB readme
Diffstat (limited to 'mongodb')
| -rw-r--r-- | mongodb/README.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/mongodb/README.md b/mongodb/README.md index 78bf954..9cf2660 100644 --- a/mongodb/README.md +++ b/mongodb/README.md @@ -38,11 +38,11 @@ recommended number of slave servers are 3.  -Sharding works by partioning the data into seperate chunks and allocating +Sharding works by partitioning the data into seperate chunks and allocating diffent ranges of chunks to diffrent shard servers. The figure above shows a collection which has 90 documents which have been sharded across the three -server: the first shard getting ranges from 1-29, and so on. When a client wants -to access a certian document it contacts the query router (mongos process), +servers: the first shard getting ranges from 1-29, and so on. When a client wants +to access a certain document, it contacts the query router (mongos process), which in turn contacts the 'configuration node', a lightweight mongod process) that keeps a record of which ranges of chunks are distributed across which shards. @@ -128,8 +128,8 @@ Build the site with the following command: --------------------------------------------- Once configuration and deployment has completed we can check replication set -availibitly by connecting to individual primary replication set nodes, 'mongo ---host 192.168.1.1 --port 2700' and issue the command to query the status of +availability by connecting to individual primary replication set nodes, `mongo +--host 192.168.1.1 --port 2700` and issue the command to query the status of replication set, we should get a similar output. @@ -150,7 +150,7 @@ replication set, we should get a similar output. "optimeDate" : ISODate("2013-03-19T10:25:55Z"), "self" : true }, - { + { "_id" : 1, "name" : "web3:2013", "health" : 1, @@ -162,8 +162,8 @@ replication set, we should get a similar output. "lastHeartbeat" : ISODate("2013-03-19T10:26:33Z"), "pingMs" : 1 } - ], - "ok" : 1 + ], + "ok" : 1 } |