Details
-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
False
-
Description
If there are no change records received, and the `debezium.source.offset.flush.interval.ms` has already passed, it seems there is no background thread that flushes the offsets.
It appears as though the offset flush interval is only used to debounce repeated calls (in `maybeFlush` method of `RecordCommitter` in the EmbeddedEngine). I could not see a mechanism to periodically flush. As a result, if I set the flush interval, for example, to 60s - and the initial sync takes a few seconds, no offset will be written.
Attachments
Issue Links
- is related to
-
DBZ-4647 snapshot_completed set to false after schema_only_recovery is run
- Open