[SERVER-15258] Expose useDeterministicHostSelection flag Created: 15/Sep/14 Updated: 08/Jan/24 Resolved: 16/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jonathan Abrahams | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | 28qa, platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Description |
|
The connection pooling for read secondary uses a random approach to determine which secondary node to read from. For testing approaches this is non-deterministic. There is a useDeterministicHostSelection flag, which changes the behavior to round-robin, but is not exposed in the shell (see https://github.com/mongodb/mongo/blob/master/src/mongo/client/replica_set_monitor.cpp). It would be useful if this could be exposed as a parameter. |
| Comments |
| Comment by Mira Carey [ 16/Feb/18 ] |
|
We've lived without this for years and it involves exposing some internals that we aren't sure we want to make public. |