[SERVER-47239] Add the "Replica set monitoring and host targeting" section to the sharding arch guide Created: 01/Apr/20  Updated: 29/Oct/23  Resolved: 27/Apr/20

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-04-20, Sharding 2020-05-04
Participants:

 Description   

Guidelines:

Should include

  • Why is it important for router nodes to monitor remote replica sets? (e.g., for $readPreference targeting)
  • What information about remote replica sets is tracked?

Code references

  • ReplicaSetMonitorManager class
  • ReplicaSetMonitor class
  • RemoteCommandTargeter class
  • SDAM spec


 Comments   
Comment by Githook User [ 27/Apr/20 ]

Author:

{'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}

Message: SERVER-47239 Add the 'Replica set monitoring and host targeting' section to the sharding arch guide
Branch: master
https://github.com/mongodb/mongo/commit/24461c383f25dbba57aa0ea20270f37a172b86b4

Comment by Haley Connelly [ 22/Apr/20 ]

This ticket now includes added a brief section inside the sharding architecture guide, and creating the client/README.md file for the service architecture guide. 

Generated at Thu Feb 08 05:13:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.