capabilities.work

Decommission a Connector

A 5-step recipe with Apache Kafka. We can help you get access.

Recipe · 5 steps

Decommission a Connector

with Apache Kafka

Archive a connector's state, shut it down cleanly, and remove it.

  1. Read the connector to confirm it exists and to capture its type and configuration for the decommission record.
  2. Capture the connector's final offsets. Without this, a rebuilt connector cannot resume where the retired one stopped and would reprocess from the beginning.
  3. Stop the connector so its tasks shut down cleanly and commit their offsets, rather than being torn down mid-flight by the delete.
  4. Delete the connector from the worker, removing its configuration and tasks from the Connect cluster.
  5. List the remaining connectors so the caller can confirm the decommission actually took effect across the Connect cluster.
What you'll need to have ready
  • connectorName: The name of the connector being decommissioned.
For your developer

Arazzo workflow apache-kafka:decommission-connector, 5 operations: getConnector → getConnectorOffsets → stopConnector → deleteConnector → listConnectors. Specs on APIs.io.

More recipes with Apache Kafka

Update a Connector ConfigurationTriage a Failed ConnectorPause and Resume a Connector for MaintenanceReset Connector OffsetsRewind Connector OffsetsValidate and Deploy a ConnectorReview Consumer Group LagGrant a Principal Access to a TopicReview Cluster and Topic CapacityDecommission a Topic