[
https://issues.apache.org/jira/browse/KAFKA-6433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16317325#comment-16317325
]
Randall Hauch commented on KAFKA-6433:
--------------------------------------
Incidentally, it would not help to change what Connect stores in the status
topic, because if the workers are using different status topics they would read
different status information. A better option might be to ship this additional
information in the metadata used in Connect's rebalance subprotocol. We can't
do this today, but we're talking about evolving the protocol for incremental
rebalance, and it'd be great to also add some additional worker metadata during
that evolution as well as tolerate optional metadata, enabling adding more
metadata fields that may not be necessary across the cluster.
> Connect distributed workers should fail if their config is "incompatible"
> with leader's
> ---------------------------------------------------------------------------------------
>
> Key: KAFKA-6433
> URL: https://issues.apache.org/jira/browse/KAFKA-6433
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 1.0.0
> Reporter: Randall Hauch
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
