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

snapshot_completed set to false after schema_only_recovery is run

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • Backlog
    • 1.8.0.Final
    • debezium-server
    • None
    • False
    • False
    • Hide

      1)  Start Debezium Server and run initial snapshot

      2) Stop Debezium Server and delete history topic

      3) Start Debezium Server with snapshot mode set to schema_only_recovery

       

       

       

      Show
      1)  Start Debezium Server and run initial snapshot 2) Stop Debezium Server and delete history topic 3) Start Debezium Server with snapshot mode set to schema_only_recovery      

    Description

      Hi there,

      This is related to another issue I've logged but seems to have a different cause.  I'm finding that if I delete the history topic and then run Debezium Server with snapshot mode schema_only_recovery, the schemas are correctly recovered, however, the offset.dat file is updated to say that snapshot_completed is now false.  If I then restart Debezium Server with snapshot mode changed to initial, it proceeds to snapshot all of the tables again, which I am assuming is not the intention?

      Attachments

        1. image-2022-01-31-23-14-32-007.png
          image-2022-01-31-23-14-32-007.png
          31 kB
        2. image-2022-01-31-23-15-26-710.png
          image-2022-01-31-23-15-26-710.png
          31 kB
        3. image-2022-01-31-23-15-46-289.png
          image-2022-01-31-23-15-46-289.png
          31 kB
        4. image-2022-02-15-13-52-40-751.png
          image-2022-02-15-13-52-40-751.png
          8 kB
        5. restart_schema_only.txt
          40 kB
        6. Start_schema_only_recovery.txt
          50 kB
        7. testing.zip
          17 kB
        8. trace_logs_schema_only_recovery.txt
          21.36 MB
        9. trace_logs_schema_only_recovery-1.txt
          21.05 MB

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. DBZ-4664 Offsets are not flushed periodically

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Open

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              nathan-smit-1 Nathan Smit
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: