@kapa.ai

2026-04-08 22:46:58 source WARN pool-2-thread-1 i.d.s.SnapshotLockProvider(lambda$createService$3):82 Found a not connector specific implementation io.debezium.snapshot.lock.NoLockingSupport for lock mode no_locking_support

The knowledge sources you provided don’t mention this specific Debezium warning message, so I can’t give a definitive, Airbyte‑specific interpretation. From the context we do have, Airbyte’s CDC connectors (MySQL, Postgres, MongoDB, MSSQL) rely on Debezium and configure snapshot behavior via

snapshot.mode

and related settings, but there is no explicit documentation or issue referencing

SnapshotLockProvider

or

no_locking_support

in these sources. [MySQL troubleshooting; MongoDB CDC properties] Given that limitation, all I can say based on the logs you shared is: • It’s a Debezium warning, not an Airbyte‑specific error. • It indicates Debezium is using a “no locking” snapshot strategy (

NoLockingSupport

) for the current connector/snapshot mode. • The provided knowledge sources do not state that this warning is harmful or how Airbyte handles it, nor do they list any remediation steps. If this warning coincides with a failing sync, you’d need to correlate it with other error messages in the logs; the current sources don’t describe such a failure pattern. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.