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?

2.1.5-Final

What is the connector configuration?

StreamSource<ChangeRecord> source = DebeziumCdcSources
        .debezium("eugene", "io.debezium.connector.mongodb.MongoDbConnector")
        .setProperty("mongodb.connection.string", "<connection string>")
        .setProperty("mongodb.members.auto.discover", "true")
        .setProperty("mongodb.name", "eugene")
        .setProperty("topic.prefix", "customer")
        .setProperty("snapshot.mode", "never")
        .setProperty("connect.keep.alive", "true")
        .setProperty("connect.keep.alive.interval.ms", "30000")
        .build();

What is the captured database version and mode of depoyment?

Hosted in the MongoDB cloud

What behaviour do you expect?

Attempts range from 0 (first) to 16 (last)

What behaviour do you see?

Attempts range from 1 (first) to 17 (last)

Do you see the same behaviour using the latest relesead Debezium version?

Yes

Do you have the connector logs, ideally from start till finish?

Yes

Error while attempting to connect to primaryPreferred node of '###' after attempt #17 (-1 remaining) 

How to reproduce the issue using our tutorial deployment?

Configure the connector to connect to a non-existing MongoDB instance and let it time out to eventual failure.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Remaining attempts: 0 looks a lot more logical than remaining attempts: -1  

Implementation ideas (optional)

<Your answer>