You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Mickael Maison (Jira)" <ji...@apache.org> on 2022/08/01 11:01:00 UTC

[jira] [Resolved] (KAFKA-14095) Improve handling of sync offset failures in MirrorMaker

     [ https://issues.apache.org/jira/browse/KAFKA-14095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mickael Maison resolved KAFKA-14095.
------------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

> Improve handling of sync offset failures in MirrorMaker
> -------------------------------------------------------
>
>                 Key: KAFKA-14095
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14095
>             Project: Kafka
>          Issue Type: Improvement
>          Components: mirrormaker
>            Reporter: Mickael Maison
>            Assignee: Mickael Maison
>            Priority: Major
>             Fix For: 3.4.0
>
>
> MirrorMaker can automatically sync offsets when sync.group.offsets.enabled is set to true. However that only works if the consumer groups are not used in the target cluster otherwise committing offsets fails with UNKNOWN_MEMBER_ID. 
> Currently we treat this case as an error in the admin client so it emits an ERROR level log line. This is misleading as it's not an unexpected error and we should treat it the same way as other group level error codes.
> In addition we should check the result of the alterConsumerGroupOffsets call in MirrorMaker and provide an helpful message in case of UNKNOWN_MEMBER_ID errors.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)