Sharding allows you to distribute load across multiple servers and keep your data balanced across those servers. This session will review MongoDB’s sharding support, including an architectural overview, design principles, and automation.
4. Examining Growth
• User Growth
– 1995: 0.4% of the world‟s population
– Today: 30% of the world is online (~2.2B)
– Emerging Markets & Mobile
• Data Set Growth
– Facebook‟s data set is around 100 petabytes
– 4 billion photos taken in the last year (4x a decade ago)
10. Data Store Scalability Today
• MongoDB Auto-Sharding
• A data store that is
– 100% Free
– Publicly available
– Open-source (https://github.com/mongodb/mongo)
– Horizontally scalable
– Application independent
12. Partitioning
• User defines shard key
• Shard key defines range of data
• Key space is like points on a line
• Range is a segment of that line
13. Data Distribution
• Initially 1 chunk
• Default max chunk size: 64mb
• MongoDB automatically splits & migrates chunks
when max reached
14. Routing and Balancing
• Queries routed to specific
shards
• MongoDB balances cluster
• MongoDB migrates data to
new nodes
15. MongoDB Auto-Sharding
• Minimal effort required
– Same interface as single mongod
• Two steps
– Enable Sharding for a database
– Shard collection within database
22. Example Cluster
• Don’t use this setup in production!
- Only one Config server (No FaultTolerance)
- Shard not in a replica set (LowAvailability)
- Only one mongos and shard (No Performance Improvement)
- Useful for developmentor demonstrating configuration mechanics
23. Starting the Configuration Server
• mongod --configsvr
• Starts a configuration server on the default port (27019)
24. Start the mongos Router
• mongos --configdb <hostname>:27019
• For 3 configuration servers:
mongos--configdb<host1>:<port1>,<host2>:<port2>,<host3>:<port3>
• This is always how to start a new mongos, even if the cluster
is already running
25. Start the shard database
• mongod --shardsvr
• Starts a mongod with the default shard port (27018)
• Shard is not yet connected to the rest of the cluster
• Shard may have already been running in production
26. Add the Shard
• On mongos:
- sh.addShard(„<host>:27018‟)
• Adding a replica set:
- sh.addShard(„<rsname>/<seedlist>‟)
27. Verify that the shard was added
• db.runCommand({ listshards:1 })
{ "shards" :
[{"_id”:"shard0000”,"host”:”<hostname>:27018”} ],
"ok" : 1
}
28. Enabling Sharding
• Enable sharding on a database
sh.enableSharding(“<dbname>”)
• Shard a collection with the given key
sh.shardCollection(“<dbname>.people”,{“country”:1})
• Use a compound shard key to prevent duplicates
sh.shardCollection(“<dbname>.cars”,{“year”:1,”uniqueid”:1})
29. Tag Aware Sharding
• Tag aware sharding allows you to control the
distribution of your data
• Tag a range of shard keys
sh.addTagRange(<collection>,<min>,<max>,<tag>)
• Tag a shard
sh.addShardTag(<shard>,<tag>)
33. Chunk splitting
• Achunk is split once it exceeds the maximum size
• There is no split point if all documents have the same shard
key
• Chunk split is a logical operation (no data is moved)
34. Balancing
• Balancer is running on mongos
• Once the difference in chunks between the most dense shard
and the least dense shard is above the migration threshold, a
balancing round starts
35. Acquiring the Balancer Lock
• The balancer on mongos takes out a “balancer lock”
• To see the status of these locks:
use config
db.locks.find({_id: “balancer”})
36. Moving the chunk
• The mongos sends a moveChunk command to source shard
• The source shard then notifies destination shard
• Destination shard starts pulling documents from source shard
37. Committing Migration
• When complete, destination shard updates config server
- Provides new locationsof the chunks
38. Cleanup
• Source shard deletes moved data
- Must wait for open cursors to either close or time out
- NoTimeoutcursors may preventthe release of the lock
• The mongos releases the balancer lock after old chunks are
deleted
59. Shard Key
• Shard key is immutable
• Shard key values are immutable
• Shard key must be indexed
• Shard key limited to 512 bytes in size
• Shard key used to route queries
– Choose a field commonly used in queries
• Only shard key can be unique across shards
– `_id` field is only unique within individual shard
60. Shard Key Considerations
• Cardinality
• Write Distribution
• Query Isolation
• Reliability
• Index Locality
Ops will be most interested in ConfigurationDev will be most interested in Mechanics
Take this slide and toss it out the window for the combined sharding talk. It’s a nice intro, but it’s more effective to spend time talking about tag aware and shard keys if you’re trying to go beyond the intro talk.
Indexes should be contained in working set.
From mainframes, to RAC Oracle servers.. People solved problems by adding more resources to a single machine.
Google was the first to demonstrate that a large scale operation could be had with high performance on commodity hardwareBuild - Document oriented database maps perfectly to object oriented languagesScale - MongoDB presents clear path to scalability that isn't ops intensive - Provides same interface for sharded cluster as single instance
In 2005, two ways to achieve datastore scalability:Lots of money to purchase custom hardwareLots of money to develop custom software
MongoDB 2.2 and later only need <host> and <port> for one member of the replica set
This can be skipped for the intro talk, but might be good to include if you’re doing the combined sharding talk. Totally optional, you don’t really have enough time to do this topic justice but it might be worth a mention.
Quick review from earlier.
Once chunk size is reached, mongos asks mongod to split a chunk + internal function called splitVector()mongod counts number of documents on each side of split + based on avg. document size `db.stats()`Chunk split is a **logical** operation (no data has moved)Max on first chunk should be 14
Balancer lock actually held on config server.
Moved chunk on shard2 should be gray
How do the other mongoses know that their configuration is out of date? When does the chunk version on the shard itself get updated?
The mongos does not have to load the whole set into memory since each shard sorts locally. The mongos can just getMore from the shards as needed and incrementally return the results to the client.
_id could be unique across shards if used as shard key.we could only guarantee uniqueness of (any) attributes if the keys are used as shard keys with unique attribute equals true
Cardinality – Can your data be broken down enough?Query Isolation - query targeting to a specific shardReliability – shard outagesA good shard key can:Optimize routingMinimize (unnecessary) trafficAllow best scaling
This section can be skipped for the intro talk, but might be good to include if you’re doing the combined sharding talk.
Reliability = if we lost an entire shard what would be the effect on the system?For most frequently used/largest indexes, how are they partitioned across shards?
Reliability = if we lost an entire shard what would be the effect on the system?For most frequently used/largest indexes, how are they partitioned across shards?
Reliability = if we lost an entire shard what would be the effect on the system?For most frequently used/largest indexes, how are they partitioned across shards?
Reliability = if we lost an entire shard what would be the effect on the system?For most frequently used/largest indexes, how are they partitioned across shards?
Compound shard key, utilize already existing (used) index, partition chunk for "power" users.For those users more than one shard *may* need to be queried in a targeted query.Reliability = if we lost an entire shard what would be the effect on the system?For most frequently used/largest indexes, how are they partitioned across shards?