Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-8691

Stopping a connector during a blocking snapshot leaves metadata in the offset file

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Low

      What Debezium connector do you use and what version?

      Version 3.0.6 across various connectors

      What is the connector configuration?

      We run an embedded engine

      What behavior do you expect?

      If a connector is stopped whilst a blocking snapshot is in progress, then the next time the connector saves the offset file, it should remove references to any in progress blocking snapshot.

      What behavior do you see?

      During a blocking snapshot, some metadata is written to the offset file:

      "snapshot":"BLOCKING","snapshot_completed":false

      If the connector is stopped during this process then this metadata is retained in the offset file. When the connector is restarted, it correctly skips snapshotting and resumes streaming. However, the blocking snapshot metadata is not cleared from the offset file. Successfully running another blocking snapshot still does not clear the metadata from the offset file.

      Whilst this is not an issue that causes any behaviour problems, it would be good to clear up afterwards, to prevent any future issues.

              Unassigned Unassigned
              benglanvillematillion Ben Glanville (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: