[KAFKA-6433] Connect distributed workers should fail if their config is "incompatible" with leader's

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.0.0
• Component/s: connect
• Labels: needs-kip
• Assignee: Unassigned
• Reporter: Randall Hauch
• Created: 08/Jan/18 23:20
• Updated: 23/Feb/18 05:50

Description

Currently, each distributed worker config must have the same `worker.id` and must use the same internal topics for configs, offsets, and status. Additionally, each worker must be configured to have the same connectors, SMTs, and converters; confusing error messages will result when some workers are able to deploy connector tasks with SMTs while others fail when they are missing plugins the other workers do have.

Ideally, a Connect workers would only be allowed to join the cluster if it were "compatible" with the the existing cluster, where "compatible" perhaps includes using the same internal topics and having the same set of plugins.

Issue Links

• is related to: KAFKA-6440 Expose Connect leader via REST
• relates to: KAFKA-5505 Connect: Do not restart connector and existing tasks on task-set change