![primary
host1
secondary
host2
secondary
host3
Python Program
monitor
thread
monitor
thread
MongoClient
{secondary: true,
hosts: ["host1",
"host2",
"host3"]}
"mongodb://host1,host2/?replicaSet=my-rs"](https://image.slidesharecdn.com/driversandhighavailability-mongodbworld2015-150601190819-lva1-app6892/75/mongodb-drivers-and-high-availability-deep-dive-8-2048.jpg?cb=1670183523)
![ismaster
(from secondary)
{"setName": "rs-name",!
"ismaster": false,!
"secondary": true,!
"hosts": ["host1", "host2", "host3"]}!](https://image.slidesharecdn.com/driversandhighavailability-mongodbworld2015-150601190819-lva1-app6892/75/mongodb-drivers-and-high-availability-deep-dive-9-2048.jpg?cb=1670183523)
![{"setName": "rs-name",!
"ismaster": true,!
"secondary": false,!
"hosts": ["host1", "host2", "host3"]}!
ismaster
(from primary)](https://image.slidesharecdn.com/driversandhighavailability-mongodbworld2015-150601190819-lva1-app6892/75/mongodb-drivers-and-high-availability-deep-dive-10-2048.jpg?cb=1670183523)
![primary
host1
secondary
host2
secondary
host3
Python Program
monitor
thread
monitor
thread
monitor
thread
MongoClient
{secondary: true,
hosts: ["host1",
"host2",
"host3"]}
"new info!"
Your
Code?
✓](https://image.slidesharecdn.com/driversandhighavailability-mongodbworld2015-150601190819-lva1-app6892/75/mongodb-drivers-and-high-availability-deep-dive-13-2048.jpg?cb=1670183523)
![primary
host1
secondary
host2
secondary
host3
Python Program
monitor
thread
monitor
thread
monitor
thread
MongoClient
{ismaster: true,
hosts: ["host1",
"host2",
"host3"]}
{secondary: true,
hosts: ["host1",
"host2",
"host3"]}
Your
Code
insert
ok
✓
✓
"new info!"
insert
ok
✓](https://image.slidesharecdn.com/driversandhighavailability-mongodbworld2015-150601190819-lva1-app6892/75/mongodb-drivers-and-high-availability-deep-dive-15-2048.jpg?cb=1670183523)
MongoDB Drivers And High Availability: Deep Dive
•2 likes•684 views
Report
Share
Download to read offline
How do MongoDB drivers discover and monitor your servers? How do they determine your replica set config, and how do they resolve a crisis like the loss of a primary? And finally, what's the best way to write your application to handle errors and outages? Staff Engineer A. Jesse Jiryu Davis covers these topics for the first time at any MongoDB conference, in his talk at MongoDB World 2015 about the new Server Discovery And Monitoring spec.
More Related Content
Viewers also liked
Viewers also liked(20)
Similar to MongoDB Drivers And High Availability: Deep Dive
Similar to MongoDB Drivers And High Availability: Deep Dive(20)
More from emptysquare
More from emptysquare(7)
Recently uploaded
![[2023] Putting the R! in R&D.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/2023puttingtherinrd-231122234738-294b2909-thumbnail.jpg?width=384&fit=bounds)
Recently uploaded(20)
![[2023] Putting the R! in R&D.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/2023puttingtherinrd-231122234738-294b2909-thumbnail.jpg?width=768&fit=bounds)
MongoDB Drivers And High Availability: Deep Dive
- 1. MongoDB Drivers & High Availability A. Jesse Jiryu Davis Staff Engineer, MongoDB @jessejiryudavis
- 2. Client Side
- 3. • It’s a MongoDB driver specification. • (It’s not MMS.) • Written by me. Advisors: David Golden, Craig Wilson, Jeff Yemin. Overseen by Bernie Hackett. Server Discovery & Monitoring Spec
- 8. primary host1 secondary host2 secondary host3 Python Program monitor thread monitor thread MongoClient {secondary: true, hosts: ["host1", "host2", "host3"]} "mongodb://host1,host2/?replicaSet=my-rs"
- 9. ismaster (from secondary) {"setName": "rs-name",! "ismaster": false,! "secondary": true,! "hosts": ["host1", "host2", "host3"]}!
- 10. {"setName": "rs-name",! "ismaster": true,! "secondary": false,! "hosts": ["host1", "host2", "host3"]}! ismaster (from primary)
- 11. Updating Topology Description Current description + ismaster response → new description
- 13. primary host1 secondary host2 secondary host3 Python Program monitor thread monitor thread monitor thread MongoClient {secondary: true, hosts: ["host1", "host2", "host3"]} "new info!" Your Code? ✓
- 14. client.db.collection.insert({'my': 'document'})! client = MongoClient(! 'mongodb://host1,host2/?replicaSet=my-rs')!
- 15. primary host1 secondary host2 secondary host3 Python Program monitor thread monitor thread monitor thread MongoClient {ismaster: true, hosts: ["host1", "host2", "host3"]} {secondary: true, hosts: ["host1", "host2", "host3"]} Your Code insert ok ✓ ✓ "new info!" insert ok ✓
- 16. Steady State
- 18. Crisis
- 22. Resolution
- 23. primary host1 secondary host2 secondary host3 monitor thread monitor thread monitor thread Your Code ✓ insert "Wake up!" (every half second) MongoClient primary host2 ✓ insert ok ok Resolution ?
- 24. So What?
- 25. client = MongoClient(! 'mongodb://host1,host2/?replicaSet=my-rs')! ! try:! client.admin.command('ismaster')! except pymongo.errors.ConnectionFailure as e:! print("Can't connect: %s" % e)! Non-Blocking Client Construction #1
- 26. Error Handling #2 def find_my_document():! try:! return collection.find_one(query)! except ConnectionFailure:! logging.exception("finding document")! return collection.find_one(query)!
- 27. Error Handling #2 def insert_doc():! doc = {'_id': ObjectId(), 'a': 1}! try:! collection.insert(doc)! except ConnectionFailure:! logging.exception("inserting document")! # Try again.! collection.insert(doc)! except DuplicateKeyError:! # Previous try actually succeeded.! pass!
- 28. #2 Error Handling collection.update(! {'_id': 1},! {'$inc': {'counter': 1}})!
- 29. #2 Only idempotent operations can be retried Error Handling
- 31. ConnectionFailure! monitor thread monitor thread monitor thread primary host1 secondary host2 secondary host3 Your Code insert insertMongoClient "Wake up!" wait for connectTimeoutMS wait for serverSelectionTimeoutMS (30 seconds)