Proposal
When exposing the mongodb cluster via mongos/AWS NLBs, we have the issue that we either risk CursorNotFound and similar errors, use session stickiness or expose one NLB per mongos.
There is another option called load_balancer_support.
We can configure most of it, but the issue is, that the LoadBalancer is using the 27017 port and the whole setup doesn't expect an additional loadBalancerPort anywhere. The proxy protocol can be enabled on the AWS NLB but it is not directly possible to configure it to forward requests to the loadBalancerPort.
Use-Case
We would like to use only one NLB (costs) instead of mongos-times the amount. But for this the mongo client needs the loadBalanced=true flag (if not using stickiness) which then again requires additional settings as described before.
Is this a feature you are interested in implementing yourself?
No
Anything else?
No response
Proposal
When exposing the mongodb cluster via mongos/AWS NLBs, we have the issue that we either risk
CursorNotFoundand similar errors, usesession stickinessor expose one NLB permongos.There is another option called load_balancer_support.
We can configure most of it, but the issue is, that the LoadBalancer is using the 27017 port and the whole setup doesn't expect an additional
loadBalancerPortanywhere. The proxy protocol can be enabled on the AWS NLB but it is not directly possible to configure it to forward requests to theloadBalancerPort.Use-Case
We would like to use only one NLB (costs) instead of mongos-times the amount. But for this the mongo client needs the
loadBalanced=trueflag (if not using stickiness) which then again requires additional settings as described before.Is this a feature you are interested in implementing yourself?
No
Anything else?
No response