2010 mongo sv-shardinginternals

1,588 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,588
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
27
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • for inconsistent read scaling\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • don’t shard by date\n\n
  • \n
  • \n
  • 2010 mongo sv-shardinginternals

    1. 1. Sharding Internals Eliot Horowitz @eliothorowitz MongoSV December 3, 2010
    2. 2. MongoDB Sharding• Scale horizontally for data size, index size, write and consistent read scaling• Distribute databases, collections or a objects in a collection• Auto-balancing, migrations, management happen with no down time
    3. 3. • Choose how you partition data• Can convert from single master to sharded system with no downtime• Same features as non-sharding single master• Fully consistent
    4. 4. Range Based MIN MAX LOCATION A F shard1 F M shard1 M R shard2 R Z shard3• collection is broken into chunks by range• chunks default to 64mb or 100,000 objects
    5. 5. Architecture Shards mongod mongod mongod ... Config mongod mongod mongod Serversmongodmongodmongod mongos mongos ... client
    6. 6. Shards• Can be master, master/slave or replica sets• Replica sets gives sharding + full auto- failover• Regular mongod processes
    7. 7. Config Servers• 3 of them• changes are made with 2 phase commit• if any are down, meta data goes read only• system is online as long as 1/3 is up
    8. 8. mongos• Sharding Router• Acts just like a mongod to clients• Can have 1 or as many as you want• Can run on appserver so no extra network traffic• Cache meta data from config servers
    9. 9. Writes• Inserts : require shard key, routed• Removes: routed and/or scattered• Updates: routed or scattered
    10. 10. Queries• By shard key: routed• sorted by shard key: routed in order• by non shard key: scatter gather• sorted by non shard key: distributed merge sort
    11. 11. Splitting• Take a chunk and split it in 2• Splits on the median value• Splits only change meta data, no data change
    12. 12. SplittingT1 MIN MAX LOCATION A Z shard1T2 MIN MAX LOCATION A G shard1 G Z shard1T3 MIN MAX LOCATION A D shard1 D G shard1 G S shard1 S Z shard1
    13. 13. Balancing• Moves chunks from one shard to another• Done online while system is running• Balancing runs in the background• Any mongos can initiate• All data transfer happens directly between shards• Once initiated, mongos can go without issue
    14. 14. MigratingT3 MIN MAX LOCATION A D shard1 D G shard1 G S shard1 S Z shard1T4 MIN MAX LOCATION A D shard1 D G shard1 G S shard1 S Z shard2T5 MIN MAX LOCATION A D shard1 D G shard1 G S shard2 S Z shard2
    15. 15. Live Migrations• Migrate initiated• Initial data copied• Delta copied until steady state + secondary ack• Start commit• Copy final delta, wait for secondary ack• Finish commit
    16. 16. DEMO
    17. 17. Download MongoDB http://www.mongodb.org and
let
us
know
what
you
think @eliothorowitz



@mongodb 10gen is hiring!http://www.10gen.com/jobs
    18. 18. User profiles• Partition by user_id• Secondary indexes on location, dates, etc...• Reads/writes know which shard to hit
    19. 19. User Activity Stream• Shard by user_id• Loading a user’s stream hits a single shard• Writes are distributed across all shards• Can index on activity for deleting
    20. 20. Photos• Can shard by photo_id for best read/write distribution• Secondary index on tags, date
    21. 21. LoggingPossible Shard Keys• date• machine, date• logger name

    ×