[CSHARP-1007] Support connecting to mongos'es behind a load balancer Created: 26/Jun/14 Updated: 01/Apr/19 Resolved: 01/Apr/19 |
|
| Status: | Closed |
| Project: | C# Driver |
| Component/s: | Connectivity |
| Affects Version/s: | 1.9.1 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Robert Stam | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Description |
|
The C# driver (and other drivers as well) do not currently support connecting to mongos'es deployed behind a load balancer, which is too bad, because deploying mongos'es behind a load balancer has many appealing operational benefits (e.g. the ease of adding/removing mongos instances without changes to the application connection string). This configuration causes a problem for the drivers, as currently implemented, because for queries that return large result sets the OP_GETMORE messages used to retrieve the next batch are sent on a different connection than the original OP_QUERY. Because the connections are through a load balancer, the OP_GETMORE messages almost invariably end up at the wrong mongos. |
| Comments |
| Comment by Jeffrey Yemin [ 01/Apr/19 ] |
|
For now, we're not going to tackle this in the C# driver, but looking into it for a new spec for all drivers. At that point, we'll open a new C# ticket linked to a DRIVERS ticket. |