Debezium on Kafka Connect
Debezium captures the changes from PostgreSQL and runs inside a Kafka Connect worker.
AvailabilityAvailable to everyone with early access to Varqeni.
How it works
- Setup: read access to the Kafka Connect REST interface through a read-only proxy, or to the Strimzi resources if Connect runs on Kubernetes.
- What it reads: the worker, the connector and every task state, with task errors.
- What it can do: resume a paused connector and restart a task left failed after an outage, only with a named approval or under your policy, through a separate executor identity.
- What it cannot do: create, delete or reconfigure connectors, or reset offsets.
What you should see: The Debezium connector part of the diagram, inside the Kafka Connect worker box.
What it can and cannot do
Can
- Read worker, connector and task state, and resume or restart within your rules.
Cannot
- Create, delete or reconfigure connectors, or reset offsets.
Related articles
- The fixes Varqeni can runTwo fixes run on pipelines and four on infrastructure. Starting a stopped virtual machine is built and switched off.
- PostgreSQLVarqeni reads your self-managed PostgreSQL through a read-only role: replication slot, write-ahead log, publication and heartbeat.
- Apicurio schema registryVarqeni checks that the schema registry answers, because changes cannot be written without it.
Still stuck? Contact support or email info@fortisdatagroup.com.