[
https://issues.apache.org/jira/browse/KAFKA-9216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17128492#comment-17128492
]
Chris Egerton commented on KAFKA-9216:
--------------------------------------
Based on [this
change|https://github.com/apache/kafka/pull/8270/files#diff-1c045c8737aea4c820319a6de65af8a4R275]
it looks like we've altered workers to fail on startup if the config topic has
multiple partitions. How should users respond in this case? As far as I know
there's no out-of-the-box tool to reduce the number of partitions for a topic.
Do we expect them to just delete the topic and then recreate it? If so, could
we say that explicitly (or even just recommend that they delete the topic and
then allow the framework to create it automatically, ACLs permitting)? If not,
can we outline a recommended flow here?
I love the idea here and it should save users plenty of headaches in the
future, but I think we might want to consider the impact on users who may see
this during an upgrade and try to outline clear steps for them to take, either
directly in the error message or on this ticket (which can be linked to in the
error message).
> 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
> Assignee: Evelyn Bayes
> Priority: Major
> Fix For: 2.3.2, 2.6.0, 2.4.2, 2.5.1
>
>
> 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)
