-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 4.4.0
-
Component/s: Replication, Shell
-
Replication
-
ALL
-
I'm trying to evaluate the split horizons feature using just a basic:
replicaSetHorizons: - "localhost": "localhost:<nodePort>"
With minikube. It doesn't seem to work with mongo shell:
mongo --tls --tlsCAFile mongo.crt --verbose "mongodb://localhost/?replicaSet=horizons"
I was curious on the implementation, so tried to isolate this further, it looks to me that this works using an undocumented property of the replicaset members named horizons, so I tried setting it myself using a single Mongo in Docker:
rs.initiate({ _id: "horizons", members: [ {_id: 0, host: "mongo", horizons: {"localhost": "localhost"}} ], }))
And got the same result. Looking at the log of the mongo shell and trying out the isMaster command for myself, it looks like the first response does indeed respent the horizons setting, but then subsequent isMaster responses from the same connection then fail to respect the horizons config (They don't persist the SNI name for awaitable/exhaust isMaster? Whatever is used today)
Using mongo from the mongo:4.4 official Docker image on Docker 19.03.12 on mac.
- duplicates
-
SERVER-50736 Make OpenSSL explicitly accept SNIs presented in ClientHello
- Closed