In Kafka Connect architecture, what is the primary role of a Worker?
Think about which component actually executes the data movement jobs.
A Kafka Connect Worker runs connectors and tasks that handle data transfer between Kafka and other systems. It does not store topics or act as a broker.
Given a Kafka Connect cluster with two workers, what is the expected output of the REST API call GET /connectors if there are three connectors named source1, sink1, and sink2?
curl -X GET http://localhost:8083/connectorsCheck the Kafka Connect REST API documentation for the format of the connectors list response.
The GET /connectors endpoint returns a JSON array of connector names as strings.
Consider a Kafka Connect task that fails to start due to a configuration error. What is the expected behavior of the Kafka Connect framework regarding this task?
Think about fault tolerance and automatic recovery in Kafka Connect.
Kafka Connect retries failed tasks with exponential backoff to handle transient errors automatically.
In distributed mode, how does Kafka Connect ensure fault tolerance and high availability of connectors and tasks?
Consider how Kafka Connect uses Kafka itself for coordination.
Kafka Connect distributed mode uses Kafka topics to coordinate multiple workers, sharing task assignments and state for fault tolerance.
You configure a Kafka Connect source connector to read from 5 partitions of an external system. The connector's tasks.max is set to 3. How many tasks will Kafka Connect create to read data?
Remember that tasks.max limits the number of tasks, but tasks can handle multiple partitions.
The connector creates up to tasks.max tasks. Since there are 5 partitions but tasks.max is 3, only 3 tasks are created. Each task can handle multiple partitions.