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

unable fetch the CDC's (Transactions) during the period when the connection was down with io.debezium.DebeziumException: The db history topic or its content is fully or partially missing

    XMLWordPrintable

Details

    • Bug
    • Resolution: Not a Bug
    • Major
    • None
    • None
    • sqlserver-connector
    • None
    • False
    • None
    • False
    • Important

    Description

       

      Bug report

      i have faced below error:

      io.debezium.DebeziumException: The db history topic or its content is fully or partially missing

       with SQL server connector version 1.9.8, i have resolved by following below steps:
      1. Deleted existing db history kafka topic (which has retention.ms  2 months and due ti that data got purged).
      2. Deleted SQL server Source connector as well
      3. Created a new connector by adding below configuration

      a. "snapshot.mode": "schema_only",
      b. "database.history.kafka.recovery.attempts": 20,
      c. "database.history.kafka.reco...": 500

      But now the issue is unable fetch the CDC's (Transactions) when the connection was down. i.e.
      My connector was down on 12th Jan 2023
      we have applied changes and created new connector on 20th Jan 2023 , In between these days there are hundreds of new transactions got created and available in DB and those transactions are not fetched by the new connector.
      Could you please advise/suggest If there is any approach that can helpful to getch the missing records for the above mentioned date.

      What Debezium connector do you use and what version?

      SQL Server - 1.9.8

      What is the connector configuration?

       

      What is the captured database version and mode of depoyment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      Kafka : MSK

      ECS: Kafka Connect

      What behaviour do you expect?

      <Your answer>

      What behaviour do you see?

      <Your answer>

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

      (Ideally, also verify with latest Alpha/Beta/CR version)

      <Your answer>

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

      (You might be asked later to provide DEBUG/TRACE level log)

      <Your answer>

      How to reproduce the issue using our tutorial deployment?

      <Your answer>

      Feature request or enhancement

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

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

      <Your answer>

      Implementation ideas (optional)

      <Your answer>

      Attachments

        Activity

          People

            Unassigned Unassigned
            ram.nkrishna@gmail.com Ramakrishna N (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: