[SERVER-19257] Configure ReplicaSetMonitorWatcher recv timeout Created: 02/Jul/15  Updated: 12/Dec/23

Status: Backlog
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.4
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Andrew Ryder (Inactive) Assignee: Backlog - Cluster Scalability
Resolution: Unresolved Votes: 0
Labels: AdiZ
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Cluster Scalability
Participants:

 Description   

RE: https://github.com/mongodb/mongo/blob/r3.1.5/src/mongo/client/replica_set_monitor.cpp#L75

The ReplicaSetMonitorWatcher thread has a hard-coded socket timeout of 5 seconds. It would be convenient in several ways if this could be configured as it would permit some coarse control over when mongos triggers re-routing decisions - particularly where tag-sets are involved. For a co-located mongos (co-located with all shards) might be appropriate to set a lower timeout, while a remotely located mongos might be better to set a little higher.


Generated at Thu Feb 08 03:50:21 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.