Bug report

What Debezium connector do you use and what version?

3.1.0.FINAL

What is the connector configuration?

can be supplied

What is the captured database version and mode of deployment?

DB on-premises

What behavior do you expect?

either the connector to stop or recover

What behavior do you see?

The connector repeatedly times out requesting the full range of receivers

If there is little change in the tables requested then the full journal range can take a long time to scan.

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

yes

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

can be supplied

How to reproduce the issue using our tutorial deployment?

A brute force way is to create a new table on a journal with a lot of log entries

start the connector with just the new table

stop the connector once snapshotting is complete

change the receiver in the offsets topic to a name that doesnt exist and restart

Implementation ideas (optional)

PR will be provided