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

Incremental snapshot caused transaction deadlock on MS SQL table

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Can't Do
    • Icon: Major Major
    • None
    • None
    • sqlserver-connector
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      1.9.3

      What is the connector configuration?

      Will attach

      What is the captured database version and mode of depoyment?

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

      MS SQL Server 2016

      On-prem kafka cluster deployed via ansible

      What behaviour do you expect?

      NO deadlocks

      What behaviour do you see?

      Deadlock on SQL table that is being incrementally snapshotted

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

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

      Haven't tried

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

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

      Will attach

      How to reproduce the issue using our tutorial deployment?

      Not sure

        1. connector_trdlplsql_LPLCustomer_ClientAccounts_source_config.json
          4 kB
        2. p1.jpg
          p1.jpg
          117 kB
        3. p2.jpg
          p2.jpg
          163 kB
        4. p3.jpg
          p3.jpg
          70 kB

              Unassigned Unassigned
              pwbriggs23 Peter Briggs (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: