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

Unhandled concurrent start and stop of Debezium Engine

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 2.6.0.Alpha2
    • None
    • embedded-engine
    • None

      When a Debezium Engine is executed in a separate thread and main thread issues close() call then it is possible that the engine was not fully initialized and ends up in a zombie state.

      The net result might be replication slot kept open or hanging transactions.

              vjuranek@redhat.com Vojtech Juranek
              jpechane Jiri Pechanec
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: