-
Bug
-
Resolution: Done
-
Major
-
1.9.3.Final
-
None
-
False
-
None
-
False
-
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Mongo Debezium connector 1.9.3.final
What is the connector configuration?
Connecting to replicasets
What is the captured database version and mode of depoyment?
Mongo 4.2 self hosted
What behaviour do you expect?
When a secondary dies the connector should continue on fine.
What behaviour do you see?
When a secondary fails we end up with an error like:
Unable to start MongoDB connector task since no replica sets were found at host1:27017,host2:27017,host3:27018
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Underlying issue
Replica set name is not populated when first server in list is unavailable
https://github.com/debezium/debezium/blob/main/debezium-connector-mongodb/src/main/java/io/debezium/connector/mongodb/ReplicaSetDiscovery.java#L99
Workaround
Disabling member discovery by setting `mongodb.members.auto.discover` to false