You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Luke Chen (Jira)" <ji...@apache.org> on 2020/08/17 03:25:00 UTC
[jira] [Assigned] (KAFKA-10401) GroupMetadataManager ignores
current_state_timestamp field for GROUP_METADATA_VALUE_SCHEMA_V3
[ https://issues.apache.org/jira/browse/KAFKA-10401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Chen reassigned KAFKA-10401:
---------------------------------
Assignee: Luke Chen
> GroupMetadataManager ignores current_state_timestamp field for GROUP_METADATA_VALUE_SCHEMA_V3
> ---------------------------------------------------------------------------------------------
>
> Key: KAFKA-10401
> URL: https://issues.apache.org/jira/browse/KAFKA-10401
> Project: Kafka
> Issue Type: Bug
> Components: offset manager
> Affects Versions: 2.1.1, 2.2.2, 2.4.1, 2.6.0, 2.5.1
> Reporter: Marek
> Assignee: Luke Chen
> Priority: Major
>
> While reading group metadata information from ByteBuffer GroupMetadataManager reads current_state_timestamp only for group schema version 2. For all other versions this value is set to "None".
> Piece of code responsible for the bug:
> [https://github.com/apache/kafka/blob/2.6.0/core/src/main/scala/kafka/coordinator/group/GroupMetadataManager.scala#L1412]
> Restarting kafka forces GroupMetadataManager manager to reload group metadata from file basically causing [KIP-211|[https://cwiki.apache.org/confluence/display/KAFKA/KIP-211%3A+Revise+Expiration+Semantics+of+Consumer+Group+Offsets]] to be only applicable for schema version 2.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)