Randall Hauch created KAFKA-9216:
------------------------------------
Summary: Enforce connect internal topic configuration at startup
Key: KAFKA-9216
URL: https://issues.apache.org/jira/browse/KAFKA-9216
Project: Kafka
Issue Type: Improvement
Components: KafkaConnect
Affects Versions: 0.11.0.0
Reporter: Randall Hauch
Users sometimes configure Connect's internal topic for configurations with more
than one partition. One partition is expected, however, and using more than one
leads to weird behavior that is sometimes not easy to spot.
Here's one example of a log message:
{noformat}
"textPayload": "[2019-11-20 11:12:14,049] INFO [Worker clientId=connect-1,
groupId=td-connect-server] Current config state offset 284 does not match group
assignment 274. Forcing rebalance.
(org.apache.kafka.connect.runtime.distributed.DistributedHerder:942)\n"
{noformat}
Would it be possible to add a check in the KafkaConfigBackingStore and prevent
the worker from starting if connect config partition count !=1 ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
