[
https://issues.apache.org/jira/browse/KAFKA-18021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17946999#comment-17946999
]
Mickael Maison commented on KAFKA-18021:
----------------------------------------
I think I ran into the MirrorCheckpointConnector issue. I described the
solution that worked for me in
https://issues.apache.org/jira/browse/KAFKA-18007?focusedCommentId=17946998&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17946998
> Disabled MirrorCheckpointConnector throws RetriableException on task config
> generation
> --------------------------------------------------------------------------------------
>
> Key: KAFKA-18021
> URL: https://issues.apache.org/jira/browse/KAFKA-18021
> Project: Kafka
> Issue Type: Bug
> Components: mirrormaker
> Affects Versions: 3.9.0
> Reporter: Greg Harris
> Assignee: TengYao Chi
> Priority: Major
> Labels: newbie
> Fix For: 4.0.0
>
>
> In KAFKA-17232, the MirrorCheckpointConnector#taskConfigs was changed to
> throw RetriableException when loadInitialConsumerGroups had not yet completed.
> When disabled, the MirrorCheckpointConnector#start method returns early, and
> never initiates the loadInitialConsumerGroups. When the
> MirrorCheckpointConnector#taskConfigs is called, it will continuously throw
> RetriableExceptions, as there is no maximum number of retries and no
> background process loading consumer groups asynchronously.
> For connectors which have never been enabled, this is a cosmetic bug,
> generating log spam but not harming the operation of the tasks.
> When changing a MirrorCheckpointConnector from enabled to disabled, this
> prevents emitting an empty set of task configs and disabling the
> already-running tasks, making it impossible to disable the
> MirrorCheckpointTasks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
