[SERVER-49500] Add maxStalenessSeconds in readPreference between mongoS and config servers Created: 14/Jul/20 Updated: 12/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Lingzhi Deng | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | 12/12, oldshardingemea | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Catalog and Routing
|
||||
| Participants: | |||||
| Story Points: | 3 | ||||
| Description |
|
I believe mongoS currently uses "nearest" without a maxStalenessSeconds option as the readPreference when communicating with the config server replica set. In the case where the "nearest" node is a lagged/stuck secondary, config reads (with afterCluserTime) may time out waiting for read concern. Adding a maxStalenessSeconds in the read preference mongoS uses seems to be an option. But I am wondering if mongoS already has other mechanism to retry such operations on a more up-to-date node. |