[DRIVERS-2080] Consider hidden members to be data-bearing nodes when TopologyType is Single Created: 13/May/19 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | SDAM |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Minor - P4 |
| Reporter: | Jeremy Mikola | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Driver Changes: | Needed | ||||||||||||
| Description |
|
In mongodb/mongo-php-library#611, a user noted that they could not create a session when connecting to a hidden replica set member in standalone mode (i.e. TopologyType Single, no "replicaSet" URI option). This is due to the fact that the spec prohibits updating the topology's logicalSessionTimeoutMinutes value based on the isMaster response of a non-data-bearing node. Under normal circumstances, applications would never communicate with a hidden replica set member; however, if an application connects directly to a hidden replica set member it does so with the intention of querying it. Therefore, I would propose amending the definition of data-bearing node to include a hidden replica set member if TopologyType is Single. |
| Comments |
| Comment by David Golden [ 14/May/19 ] |
|
Seems reasonable. Seems related to SPEC-1248 and the idea of separating "what can I do with the node I'm talking to?" from "how am I monitoring and routing requests?" |