[DRIVERS-603] Add support for Split-Horizon Topology Created: 30/Oct/18  Updated: 27/May/22  Resolved: 29/Apr/19

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Epic Priority: Major - P3
Reporter: Scott L'Hommedieu (Inactive) Assignee: Unassigned
Resolution: Won't Fix Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CDRIVER-2944 Add support for Split-Horizon Topology Closed
depends on CSHARP-2503 Add support for Split-Horizon Topology Closed
depends on CXX-1729 Add support for Split-Horizon Topology Closed
depends on GODRIVER-808 Add support for Split-Horizon Topology Closed
depends on JAVA-3165 Add support for Split-Horizon Topology Closed
depends on MOTOR-308 Add support for Split-Horizon Topology Closed
depends on NODE-1858 Add support for Split-Horizon Topology Closed
depends on PHPC-1323 Add support for Split-Horizon Topology Closed
depends on PYTHON-1737 Add support for Split-Horizon Topology Closed
depends on RUBY-1701 Add support for Split-Horizon Topology Closed
depends on RUST-140 Add support for Split-Horizon Topology Closed
Related
Server Compat: 4.2
Driver Compliance:
Key Status/Resolution FixVersion
NODE-1858 Gone away
JAVA-3165 Gone away
SCALA-494 Gone away
PYTHON-1737 Gone away 3.9
PHPC-1323 Gone away
CXX-1729 Gone away
CDRIVER-2944 Gone away 1.15.0
MOTOR-308 Gone away
CSHARP-2503 Done
GODRIVER-808 Gone away 1.1.0
PERL-1064 Gone away
RUBY-1701 Done
RUST-140 Gone away

 Description   

Support the use of different addresses reported via isMaster to connect to a mongo process depending on which network the process is on.



 Comments   
Comment by Ian Whalen (Inactive) [ 18/Mar/19 ]

scott.lhommedieu I'm bumping this from 4.2 given that there's pretty substantive open debate over whether there's any drivers changes needed here. If it does land that there are drivers changes needed, can you bump it into 4.2 and I can push it forward from there.

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