Context
We found in serverless tests that Go driver uses OP_QUERY with isMaster in load balancer mode. Howerver, the spec says OP_MSG must be used.
[2023/10/02 17:49:04.806] [ProxySession(60e60c6ccbd24f21a039c13a_,10673-drivers-testing-lb.2tzoa.mongodb-dev.net,3.236.71.14:54856).debug] [session_proxy.go:handleQueryMessage:498] got OP_QUERY isMaster [2023/10/02 17:49:04.806] [ProxySession(60e60c6ccbd24f21a039c13a_,10673-drivers-testing-lb.2tzoa.mongodb-dev.net,3.236.71.14:54856).info] [session_proxy.go:handleClientMetadata:407] received client metadata from 3.236.71.14:54856:{"driver":{"name":"mongo-go-driver","version":"v1.13.0-prerelease"},"os":{"type":"linux","architecture":"amd64"},"platform":"go1.20.8"}
Definition of done
Hello commamnd with OP_MSG is used instead.
Pitfalls
What should the implementer watch out for? What are the risks?
- is depended on by
-
DRIVERS-2783 Test that LoadBalanced connection handshake uses OP_MSG
- Backlog
- related to
-
GODRIVER-2892 Remove all code that is only required for MongoDB 3.4 and earlier
- Closed
-
GODRIVER-2935 Use OP_QUERY in connection handshakes
- Closed